[Slackbuilds-users] Ruby gems packaging policies

JK Wood joshuakwood at gmail.com
Tue Nov 18 17:04:27 UTC 2008


Anytime I've installed a gem, it handled the dependencies on its own.
That's built in to Ruby gems.

On Tue, Nov 18, 2008 at 8:42 AM, Marco Bonetti
<marco.bonetti at slackware.it>wrote:

> On Tue, November 18, 2008 15:22, Vincent Batts wrote:
> > either that or just let gem do its own management, since it can keep up
> > with versions/updates and dependency resolution for gems.
> yes, it's cool, but the problem arise since the gem is a dependency and
> not the final package :-/
> I'll experiment a little as soon as I get to my build machine.
>
> ciao
>
> --
> Marco Bonetti
> BT3 EeePC enhancing module: http://sid77.slackware.it/bt3/
> Slackintosh Linux Project Developer: http://workaround.ch/
> Linux-live <http://workaround.ch/Linux-live> for powerpc:
> http://workaround.ch/pub/rsync/mb/linux-live/
> My webstuff: http://sidbox.homelinux.org/
>
> My GnuPG key id: 0x86A91047
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20081118/eb3b79e7/attachment.htm>


More information about the SlackBuilds-users mailing list