[Slackbuilds-users] Ruby gems packaging policies

[Vincent Batts]

> Partially answering to myself with:
> http://www.rubygems.org/read/chapter/13#page43
> I will try "gem install $PKG/$GEM_PATH" with a previous source of the
> profile.d file a la kde slackbuild.
>
> ciao
>

either that or just let gem do its own management, since it can keep up
with versions/updates and dependency resolution for gems. i understand
wanting to see a 'rails' or 'mongrel' package specifically, and i know
other distributions have begun to package them like that, but you start
running into questions like should package ActiveRecord, etc. in with the
rails package, or just have many individual packages, with detailed
README's
this kindof defeats the purpose of rubygems, especially on slackware's
package management.

vb

> --
> Marco Bonetti
> BT3 EeePC enhancing module: http://sid77.slackware.it/bt3/
> Slackintosh Linux Project Developer: 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/
>
>


-- 
vb

http://hashbangbash.com/