ubuntu-on-rails team mailing list archive

[John Leach <john@xxxxxxxxxxxxxxx>]

On Tue, 2011-03-15 at 15:58 +0200, Antono Vasiljev wrote:
> On Tue, 2011-03-15 at 12:30 +0000, John Leach wrote:

> > I did notice that it is storing gems in /usr/lib/rubinius/gems whereas
> > the mri rubygems package stores them in /var/lib/gems  Is there some
> > reason it can't use /var/lib/gems ?
> 
> Yes, This part is still a little bit ugly koz rubinius provide
> pre-installed gems and they should be installed in location different
> from /var/lib/gems in order to not be owerwritten by gem command.
> 
> Probably right way is to move preinstalled gems to /usr/lib/rubinius and
> use /var/lib/gems for gems installed via rubygems. But this requires
> some hacking on rubinius side.
> 
> What do You think?

well, actually, now I think about it a bit more, var is meant for
changing data but a gem is a library, so installing in /usr/lib isn't
exactly wrong.

I suppose the Debian folk have decided that gems are more appropriate
in /var/lib so I'd suspect that your package would be more likely to be
accepted upstream if it did the same.

So yeah, I think you're right, preinstalled gems in /usr/lib/rubinius
and /var/lib/gems for user instaled gems.

I'm sure the rubinius devs would be open to having rubinius configurable
for that situation (the rubygems team were, they added hooks especially
to make packaging easier) - ask upstream for it.

John.