Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Plugins sandbox for each Vagrantfile #10
@thedrow do you have an idea on how to implement this? I have looked at
The minimum I would want to achieve is #6. This would mean that whenever you switch to a Vagrantfile with different plugin requirements, it would uninstall the not-required ones (maybe this should be optional) and ensure that the required plugins are installed in the correct version (which might mean re-installing an existing plugin in a different version).
The thing that makes me headaches is that you can not run Vagrant in parallel anymore if you have different plugin requirements (and if the required plugins would be installed automatically - which I considered as a configuration option for #6).
IMHO this plugin can be only a workaround until it is properly fixed in vagrant itself: see hashicorp/vagrant#1789 or mitchellh/vagrant/issues#1874
Ok, this exact action should be replaced.
What should be changed is line 35. Also the uninstallation process should be modified.
installer = Gem::DependencyInstaller.new(:document => , :prerelease => prerelease)
I think that the
@tknerr What do you think?
referenced this issue
Jun 29, 2013
@thedrow cool, thanks for the investigation
I'm not sure whether this should be solved outside of vagrant, or whether vagrant should allow for having multiple versions of a plugin installed. Let's see what @fgrehm and @mitchellh opinion is on this (see discussion in hashicorp/vagrant#1874).
But as of today, I don't see any other possibility than you suggested.