Re: [Puppet Users] Re: [Puppet-dev] Re: Announce: Puppet 3.0.0 Live

2012-10-01 Thread Jos Backus
Hi Matthaus, On Monday, October 1, 2012 4:25:02 PM UTC-7, Matthaus Litteken wrote: > > The builds of puppet require ruby, but are built with ruby 1.8 (at > least on EL 5 and 6, and Fedora 15 and 16), so > they put all of puppet's lib in the sitelibdir of the ruby they were > built with, so they

Re: [Puppet-dev] Re: Announce: Puppet 3.0.0 Live

2012-10-01 Thread Jos Backus
Hi Jeff, On Monday, October 1, 2012 4:14:05 PM UTC-7, Jeff McCune wrote: > > On Mon, Oct 1, 2012 at 2:44 PM, Jos Backus > > wrote: > > Hi, > > > > Any chance we will see Ruby 1.9-compatible RPMs for Puppet 3.0.0 and > Facter > > 2.0.0 soon? > > Jos, > > We're currently building and maintai

Re: [Puppet Users] Re: [Puppet-dev] Re: Announce: Puppet 3.0.0 Live

2012-10-01 Thread Matthaus Owens
The builds of puppet require ruby, but are built with ruby 1.8 (at least on EL 5 and 6, and Fedora 15 and 16), so they put all of puppet's lib in the sitelibdir of the ruby they were built with, so they go in /usr/lib/ruby/site_ruby/1.8 . For EL, we support whatever ruby distros have available and

Re: [Puppet-dev] Re: Announce: Puppet 3.0.0 Live

2012-10-01 Thread Jeff McCune
On Mon, Oct 1, 2012 at 2:44 PM, Jos Backus wrote: > Hi, > > Any chance we will see Ruby 1.9-compatible RPMs for Puppet 3.0.0 and Facter > 2.0.0 soon? Jos, We're currently building and maintaining our own ruby 1.8.7 packages and the Puppet and Facter RPM's depend on these. What Ruby 1.9 packages

[Puppet-dev] Re: Announce: Puppet 3.0.0 Live

2012-10-01 Thread Jos Backus
Hi, Any chance we will see Ruby 1.9-compatible RPMs for Puppet 3.0.0 and Facter 2.0.0 soon? Thanks, Jos -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/

Re: [Puppet-dev] Announce: Puppet 3.0.0 Live

2012-10-01 Thread Aaron Grewell
On Mon, Oct 1, 2012 at 11:12 AM, Andy Parker wrote: > On Fri, Sep 28, 2012 at 4:15 PM, Aaron Grewell > wrote: >> On Fri, Sep 28, 2012 at 2:49 PM, Michael Stahnke >> wrote: >>> Puppet 3.0.0 is a feature release for the 3.x series of Puppet. > > On the whole what I want to see if a 3.x line of p

Re: [Puppet-dev] Announce: Puppet 3.0.0 Live

2012-10-01 Thread Andy Parker
On Fri, Sep 28, 2012 at 4:15 PM, Aaron Grewell wrote: > On Fri, Sep 28, 2012 at 2:49 PM, Michael Stahnke > wrote: >> Puppet 3.0.0 is a feature release for the 3.x series of Puppet. > >> * Semantic Versioning - With 3.0.0, Puppet Labs makes a commitment to >> follow the Semantic Versioning guidel

Re: [Puppet-dev] evaluate variables from a config file

2012-10-01 Thread Darin Perusich
I'll take a look at this. Thanks Gary! -- Later, Darin On Mon, Oct 1, 2012 at 12:48 PM, Gary Larizza wrote: > I always like looking back at the work RI did in the facts-dot-d > facter fact for something like this --> > https://github.com/ripienaar/facter-facts/blob/master/facts-dot-d/facter_do

Re: [Puppet-dev] evaluate variables from a config file

2012-10-01 Thread Gary Larizza
I always like looking back at the work RI did in the facts-dot-d facter fact for something like this --> https://github.com/ripienaar/facter-facts/blob/master/facts-dot-d/facter_dot_d.rb#L39-51 On Mon, Oct 1, 2012 at 9:46 AM, Darin Perusich wrote: > Hello, > > What is the best way to evaluate the

[Puppet-dev] evaluate variables from a config file

2012-10-01 Thread Darin Perusich
Hello, What is the best way to evaluate the variables set in a config file in a provider? The variables in the file are setup like MY_VAR="foo bar baz". I currently have this little piece of code working but it's certainly not very elegant so I'm looking for some guidance. IO.read(/some/file.cfg

Re: [Puppet-dev] Parse command output in a privoder

2012-10-01 Thread Darin Perusich
Thanks Markus! -- Later, Darin On Sun, Sep 30, 2012 at 4:47 PM, markus wrote: > >> I'm working on a provider and it needs to parce the output from a >> command that's space separated on a single line. So far I've been >> unsuccessful at splitting it up so I can loop thru the values to see >> if