[aur-general] Packaging a Ruby application (veewee) with embedded gems (no dependency on Arch ruby-* packages)

Jonathan Steel mail at jsteel.org
Thu Apr 10 18:23:15 EDT 2014

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://mailman.archlinux.org/pipermail/aur-general/attachments/20140410/3e2c1233/attachment.asc>

More information about the aur-general mailing list