> -----Original Message----- > From: puppet-users@googlegroups.com [mailto:puppet- > us...@googlegroups.com] On Behalf Of Robin Lee Powell > Sent: Friday, April 01, 2011 4:40 AM > To: Puppet Users > Subject: [Puppet Users] gems, ruby installs, and paths > > > I'm working on a system (not created by me, I swear) that has > something like 5 different versions of ruby installed, including a > couple of versions of jruby. > > I need to install a gem, but I need to use /opt/jruby/bin/gem (or > jgem) to do it. > > Unfortunately, I can't see any way to modify puppet's path to help > it find this little "gem" (ha ha). > > Is path modification like this possible? > > Is there another/better way to handle this issue? > > Of course I could use an "exec", but I try to avoid those whenever > at all possible since it rather defeats the purpose of using puppet > (see > http://utcc.utoronto.ca/~cks/space/blog/programming/ConfiguringInRealLa > nguage > )
In a similar situation (ruby-1.8.x and REE installed on a server), I found that mangling the PATH to point at the appropriate ruby did it. That only works if your entire puppet config (including puppet itself?) works with that ruby, of course. Otherwise, I think the exec is it. Unless someone (one of us?) patches the gem provider to take a PATH? I don't know if that's useful for anything other than the sad case of too many rubys (rubies?) being installed at once, or if this is a common problem. -- Bill Weiss Backstop Solutions Group -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
