On 28.06.2016 17:50, Adam Števko wrote:
Yes, I did and got vagrant working as separate ruby gems. The main problem with
this approach is that packaging every needed gem is too much work and
maintenance cost is high. Also, Vagrant webpage doesn’t recommend using
gem-based deployment of Vagrant and packages from the official site as
recommended. They contain every dependency and Vagrant is self-contained (and
it’s much harder to break it!). I tried looking at what would take to
contribute OpenIndiana support to the upstream and found out that their build
system uses Puppet.
I’d appreciate if there is somebody in the community willing to do the work and
extend those Puppet manifests and contribute it upstream. I’ll provide and
maintain the build infrastructure behind it. With OpenIndiana as a first class
citizen, the Vagrant team will do releases (if somebody wants to have an IPS
package from it, we can make that happen from official release). This way, we
will have regular Vagrant fixes and releases and also be sure that nothing in
OI can break it.
Cheers,
Adam
Hi Adam
Arch Linux seems to have found a tar.gz of the upstream packages that it
repackages as arch package.
Have a look at
https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/vagrant
Maybe that would also be a way to get vagrant installed.
Greetings
Till
_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
