> -----Original Message----- > From: Nigel Kersten [mailto:ni...@puppetlabs.com] > Sent: Saturday, April 02, 2011 7:05 PM > To: puppet-users@googlegroups.com > Cc: Bill Weiss > Subject: Re: [Puppet Users] gems, ruby installs, and paths > > On Sat, Apr 2, 2011 at 4:29 PM, Bill Weiss > <bwe...@backstopsolutions.com> wrote: > > > 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. > > The gem package provider doesn't specify a given PATH for the gem > command. > > If you construct your PATH for the puppet process such that the > desired gem is found first, that will work, but doesn't solve the > problem some people have with wanting to use several different gem > executables within the same puppet run.
Right. I meant the OS PATH, not the PATH inside of Puppet. Thanks for the clarification, Nigel. -- 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.
