On Sat, Apr 02, 2011 at 05:05:18PM -0700, Nigel Kersten wrote:
> On Sat, Apr 2, 2011 at 4:29 PM, Bill Weiss
> 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 en
> -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
On Sat, Apr 2, 2011 at 4:29 PM, Bill Weiss 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
> -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
No-one has hit this issue? I'm really surprised.
-Robin
On Fri, Apr 01, 2011 at 02:39:35AM -0700, Robin Lee Powell wrote:
>
> 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
