Created attachment 414958 [details] vagrant-bin-1.7.4.ebuild The app-emulation/vagrant package is abandoned as it needs significant human resources to keep up to date. Let's introduce a bin package for those who which to use it. I will proxy maintain the package, help is welcome of course.
Created attachment 414960 [details] vagrant-bin-1.7.4.ebuild Making Virtualbox optional: https://docs.vagrantup.com/v2/providers/index.html
Created attachment 414962 [details] vagrant-bin-1.7.4.ebuild Making repoman happy :)
Will check on status of the actual vagrant first.
We kinda don't wanna install an rpm. Check the source code here: https://github.com/mitchellh/vagrant/blob/master/vagrant.gemspec
Hello Manuel. Yes, I've also checked the list, I even tried installing it by hand and it seems we're missing at least these packages in Gentoo: Using fake_ftp 0.1.1 Using gssapi 1.2.0 Using gyoku 1.3.1 Using hashdiff 0.2.2 Using hashicorp-checkpoint 0.1.4 Using rb-fsevent 0.9.6 Using mini_portile 0.6.0 Using nori 2.6.0 Using rb-kqueue 0.2.4 Using wdm 0.1.1 Using winrm 1.3.4 Using winrm-fs 0.2.2 Now the question is, are we going to postpone the package until all is resolved or we add a bin package and slowly add the deps just for vagrant? Packages like hashicorp-checkpoint (Internal HashiCorp service to check version information)? Yes I know we don't want to use rpms, but we are actually using them anyways, we have binary packages.
This is how we handle stuff in ruby, package deps that are required. Drop deps that are not necessary. We only serve binaries if it's not possible otherwise. Check for missing packages here: http://gpo.zugaina.org/
I know it is frustrating to have -bin packages. But vagrant can be rather useful for some deployment testing and I would love to use it on gentoo. I personally would appreciate to have a recent version (>= 1.7.3 needed for >=virtualbox-5.0) to work with. The -bin version 1.7.4 works with my current Virtualbox-5.0.10! Thanks Thomas!
A while ago, I made a weekend effort to package vagrant-1.8.0 and vagrant-libvirt including all but the windows-stuff dependencies. If this is any help, you can clone my overlay from https://linuxmonk.ch/overlay (sorry, no web interface).
(In reply to Reto Gantenbein (ganto) from comment #8) > A while ago, I made a weekend effort to package vagrant-1.8.0 and > vagrant-libvirt including all but the windows-stuff dependencies. If this is > any help, you can clone my overlay from https://linuxmonk.ch/overlay (sorry, > no web interface). Hi Reto, thanks for that! Are you willing to proxy maintain vagrant and friends? I don't have much ruby experience yet, but can help out. What do you think? I'm sure once we put up the ebuilds into portage, the ruby team will help us also.
While I do think it would be cool to install Vagrant 'natively' without the binary build, I am not sure how much work it would be to maintain that. My concern is that with the advent of their binary builds, I feel the Vagrant team is much more willing to do 'whatever is necessary' to make the next build work (which could mean grabbing (and possibly forking) random dependencies). If they choose to fork dependencies for Vagrant-specific changes but don't send to upstream and get it merged before a release, it would be really awful to see a lot of vagrant-some-ruby-package ebuilds as a result. A compromise of latest vs pure would be to have both -bin (which is relatively trivial to update) and the native ebuild. Also, with regards to the native build, will plugins work? Will plugins need their own ebuilds? At the very least, many users would expect to see plugins like vagrant-vbguest (which allows extra customisation of a VirtualBox VM).
As far as I see it, the problem wouldn't really be to maintain the vagrant ebuild itself. The real work is the Rubygem dependency chain that vagrant requires. Myself, I'm also not at all a Ruby enthusiast and to be honest, I went through hell to ebuild-ify them all, especially if you also like the test suites to succeed. Why does every Rubygem use a different test framework...? Also fog is a super beast by itself. I'm glad I made this experience, but I'm definitely the wrong one to ask for maintaining Ruby stuff. This needs someone with a lot of affection and patience for Ruby. @Andrew: In my overlay you can find ebuilds for vagrant-libvirt and vagrant-lxc. They both work perfectly. Also you can easily install new plugins with your user into your personal VAGRANT_HOME. However, if the global Gem versions is not exactly what the plugin expects, you end up installing all dependencies again for your user.
Created attachment 422538 [details] vagrant-bin-1.8.1.ebuild
You can test this: https://github.com/gentoo/gentoo/pull/677
A binary version will not be in Gentoo.
