10 Apr
2014
10 Apr
'14
10:23 p.m.
On Thu 10 Apr 2014 at 20:42, Bertrand Bonnefoy-Claudet wrote:
[...]
vagrant has recently been accepted in community and has a PKGBUILD that I find peculiar. It seems like it uses some embedded directory to store gems it depends on. [...]
There wasn't really a choice; I intended to install it "properly" (not in /opt) and bring the ruby dependencies over to [community] with it, but while testing the package in the AUR I found this was the only way to package Vagrant so that it would work with plugins like vagrant-{login,share} and the vmware plugin. So it's more of an upstream decision to package it this way. iirc the deb and rpm packages install the same way. -- Jonathan Steel