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
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
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
[EMAIL PROTECTED]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
JK Wood wrote:
Anytime I've installed a gem, it handled the dependencies on its own.
That's built in to Ruby gems.
I think what he means is he has a non-gem app with a dependency on a gem. And
he's asking for a proper way to handle that case.
Grs,
Heinz
signature.asc
Description: This is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Heinz Wiesinger wrote:
I think what he means is he has a non-gem app with a dependency on a gem. And
he's asking for a proper way to handle that case.
straight to the point.
do I really write such an awful english? :D
- --
Marco Bonetti
BT3 EeePC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Heinz Wiesinger wrote:
I think what he means is he has a non-gem app with a dependency on a
gem. And
he's asking for a proper way to handle that case.
straight to the point.
do I really write such an awful english? :D
OH, well then i would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Batts wrote:
because it would not need a separate application installed with it,
plus that could potentially stomp on someone's existing installation.
good point, I'll choose this way.
thanks for the help!
- --
Marco Bonetti
BT3 EeePC 70x
