<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 09/24/2013 07:51 AM, Alexandre
Drahon wrote:<br>
</div>
<blockquote
cite="mid:1549207910.711843.1380023488331.JavaMail.root@redhat.com"
type="cite">
<div style="font-family: Arial; font-size: 12pt; color: #000000">
<div>Hi Mo,<br>
</div>
<div><br>
</div>
<div>Thanks for the pointers, I'll definitely look at this and
ask for help on the Ruby SIG list. The issue here is that
Vagrant plugins are rubygems that get installed in the user's
~/.vagrant.d/ directory with all their dependencies (ie.
Vagrant won't reuse system-wide installed gems). I already
face the issue with vagrant-kvm with the dependency on
Nokogiri, which needs gcc to install. OTOH I'm trying to keep
Vagrant patching to a minimum. I think the best course of
action is:<br>
</div>
<div> - have Vagrant look for plugins system-wide first (in
/usr/share/gems) and then in ~/.vagrant.d<br>
</div>
<div> - still allow plugin install from rubygems.org ('vagrant
plugin install whatever') and ensure it works<br>
</div>
<div> - provide vagrant-kvm as a system-wide rubygem and ensure
it uses system-wide dependencies <br>
</div>
<div> - maybe provide some other Vagrant plugins as RPM (not
sure it's wise)<br>
</div>
<div><br>
</div>
<div>bundler_ext seems like it could help here, I'm going to
have a look at that.<br>
</div>
<div><br>
</div>
<div>Alex<br>
</div>
</div>
</blockquote>
<br>
Sounds like the plugin system works somewhat similar to engines in
rails. IIUC, so long as we have the deps to startup the base system
from a yum install, we should be good as far as loading plugins from
wherever. Additional plugins shipped as rpm's would be a nice
feature but might not be a required from the get-go.<br>
<br>
-Mo<br>
</body>
</html>