3 ms·

Probably not the right venue, but I'm a bit disappointed addressing the plugin versioning situation isn't listed as a thing for 1.5. There are plugins for manag

Probably not the right venue, but I'm a bit disappointed addressing the plugin versioning situation isn't listed as a thing for 1.5. There are plugins for managing plugins but they're really less than ideal. I'd honestly just like to use bundler for it, since it's almost certainly better than anything anyone's likely to make to replace it, but using bundler to run vagrant is currently considered bad for some reason and outputs a frightening warning.

mitchellh 13y ago
Bundler doesn't work with Vagrant because Vagrant ships with its own Ruby and RubyGems and all that. So... your Bundler you're executing has a really screwed up state of the world. Its something that certainly needs to be solved, but I think solutions needs more time to mature in my head as well as others.
- stormbrew 13y ago
  The problem right now is that plugins create a screwed up state of the world and their usefulness is rapidly climbing. Installing the vagrant-chef-zero plugin, for example, is a real PITA because the dependency resolution doesn't deal with a json dependency correctly leading to it or chef zero failing to load unless you install them in a very specific order. On the other end of the spectrum, when you're writing a Vagrantfile it's technically almost impossible to know what's going to happen when a user starts it up because of all the hooks plugins can throw in, and you can't tell Vagrant not to load a plugin (which would be an incomplete solution anyways, since I can't know what plugins or plugin versions will have bad interactions). I know you wrote vagrant, so you have a more inside perspective on this, but as a user and occasional plugin writer, it feels like with a gemfile I can specify a state of the world that's considerably less screwed up than the completely random world any given user's install of Vagrant might be.

mitchellh 13y ago

Bundler doesn't work with Vagrant because Vagrant ships with its own Ruby and RubyGems and all that. So... your Bundler you're executing has a really screwed up state of the world. Its something that certainly needs to be solved, but I think solutions needs more time to mature in my head as well as others.

stormbrew 13y ago
The problem right now is that plugins create a screwed up state of the world and their usefulness is rapidly climbing. Installing the vagrant-chef-zero plugin, for example, is a real PITA because the dependency resolution doesn't deal with a json dependency correctly leading to it or chef zero failing to load unless you install them in a very specific order. On the other end of the spectrum, when you're writing a Vagrantfile it's technically almost impossible to know what's going to happen when a user starts it up because of all the hooks plugins can throw in, and you can't tell Vagrant not to load a plugin (which would be an incomplete solution anyways, since I can't know what plugins or plugin versions will have bad interactions). I know you wrote vagrant, so you have a more inside perspective on this, but as a user and occasional plugin writer, it feels like with a gemfile I can specify a state of the world that's considerably less screwed up than the completely random world any given user's install of Vagrant might be.