I am having no joy installing Puppet Server with MySQL support from the EPEL on Centos 6. The active record support for MySQL seems to be missing. Has anyone seen a good howto for this? -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 10/17/2011 04:14 PM, robert.mortimer@gmail.com wrote:> I am having no joy installing Puppet Server with MySQL support from > the EPEL on Centos 6. The active record support for MySQL seems to be > missing. Has anyone seen a good howto for this? >You would need to install mysql library for Ruby. It should be packed in Centos. -- Dominik Zyla -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Oct 17, 3:46 pm, Dominik Zyla <dominik.z...@gmail.com> wrote:> On 10/17/2011 04:14 PM, robert.morti...@gmail.com wrote: > > > I am having no joy installing Puppet Server with MySQL support from > > the EPEL on Centos 6. The active record support for MySQL seems to be > > missing. Has anyone seen a good howto for this? > > You would need to install mysql library for Ruby. It should be packed in > Centos. > > -- > Dominik ZylaOK I was getting "ERROR: Could not find a valid gem ''ActiveRecord'' (>= 0) in any repository" And that was sending me off on a wild goose chase across the internet looking for a Centos 6 ActiveRecord. Found it just as I came back to check Rob -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Oct 17, 4:00 pm, "robert.morti...@gmail.com" <robert.morti...@gmail.com> wrote:> On Oct 17, 3:46 pm, Dominik Zyla <dominik.z...@gmail.com> wrote: > > > On 10/17/2011 04:14 PM, robert.morti...@gmail.com wrote: > > > > I am having no joy installing Puppet Server with MySQL support from > > > the EPEL on Centos 6. The active record support for MySQL seems to be > > > missing. Has anyone seen a good howto for this? > > > You would need to install mysql library for Ruby. It should be packed in > > Centos. > > > -- > > Dominik Zyla > > OK I was getting > "ERROR: Could not find a valid gem ''ActiveRecord'' (>= 0) in any > repository" > And that was sending me off on a wild goose chase across the internet > looking for a Centos 6 ActiveRecord. >Still no joy I get this on the master when I run the client: Could not connect to database: Please install the mysql adapter: `gem install activerecord-mysql-adapter` (Could not find RubyGem mysql (~> 2.8.1)#012) ruby-mysql.x86_64 is installed but is ruby-mysql.x86_64 2.8.2-1.el6 from the epel Config is as follows (not real password) [master] storeconfigs = true dbadapter = mysql dbuser = puppet dbpassword = PASSWORD_HR dbserver = lsg-cbp-mysql01 dbname = puppet #dbsocket = /var/lib/mysql/mysql.sock Connection string can be used to connect to DB server from puppet server command line Do I need the Exact ruby mysql?> Found it just as I came back to check > > Rob-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Personally, I''ve had better luck letting gem managed its own gems, rather than depending on Yum repositories (specifically on CentOS). I''d take a list of the Ruby gems you''ve installed via rpm (rpm -q -a | grep ruby) and then consider installing them directly, as so: % sudo gem install mysql % sudo gem list Regards, Russell On Mon, Oct 17, 2011 at 12:57 PM, robert.mortimer@gmail.com < robert.mortimer@gmail.com> wrote:> > > On Oct 17, 4:00 pm, "robert.morti...@gmail.com" > <robert.morti...@gmail.com> wrote: > > On Oct 17, 3:46 pm, Dominik Zyla <dominik.z...@gmail.com> wrote: > > > > > On 10/17/2011 04:14 PM, robert.morti...@gmail.com wrote: > > > > > > I am having no joy installing Puppet Server with MySQL support from > > > > the EPEL on Centos 6. The active record support for MySQL seems to be > > > > missing. Has anyone seen a good howto for this? > > > > > You would need to install mysql library for Ruby. It should be packed > in > > > Centos. > > > > > -- > > > Dominik Zyla > > > > OK I was getting > > "ERROR: Could not find a valid gem ''ActiveRecord'' (>= 0) in any > > repository" > > And that was sending me off on a wild goose chase across the internet > > looking for a Centos 6 ActiveRecord. > > > Still no joy I get this on the master when I run the client: > > Could not connect to database: Please install the mysql adapter: `gem > install activerecord-mysql-adapter` (Could not find RubyGem mysql (~> > 2.8.1)#012) > > ruby-mysql.x86_64 is installed but is ruby-mysql.x86_64 2.8.2-1.el6 > from the epel > > Config is as follows (not real password) > > [master] > storeconfigs = true > dbadapter = mysql > dbuser = puppet > dbpassword = PASSWORD_HR > dbserver = lsg-cbp-mysql01 > dbname = puppet > #dbsocket = /var/lib/mysql/mysql.sock > > Connection string can be used to connect to DB server from puppet > server command line > > Do I need the Exact ruby mysql? > > > Found it just as I came back to check > > > > Rob > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
robert.mortimer@gmail.com wrote:> I am having no joy installing Puppet Server with MySQL support from > the EPEL on Centos 6. The active record support for MySQL seems to be > missing. Has anyone seen a good howto for this?Sadly, rubygem-rails is not built for EL-6. You can either rebuild the 2.3.8 packages from Fedora or find someone to act as a maintainer for these in EPEL. -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A word to the wise ain''t necessary -- it''s the stupid ones who need the advice. -- Bill Cosby
On Oct 17, 9:05 pm, Todd Zullinger <t...@pobox.com> wrote:> robert.morti...@gmail.com wrote: > > I am having no joy installing Puppet Server with MySQL support from > > the EPEL on Centos 6. The active record support for MySQL seems to be > > missing. Has anyone seen a good howto for this? > > Sadly, rubygem-rails is not built for EL-6. You can either rebuild > the 2.3.8 packages from Fedora or find someone to act as a maintainer > for these in EPEL.But the puppet was from the epel, I sort of assumed it would have the correct mysql When I attempt the gem install I get:- gem install mysql --with-mysql-include=/usr/include/mysql --with- mysql-libs=/usr/lib64/mysql /usr/lib/ruby/1.8/thread.so: /usr/lib/ruby/1.8/thread.so: wrong ELF class: ELFCLASS32 - /usr/lib/ruby/1.8/thread.so (LoadError) from /usr/lib/ruby/1.8/thread.rb:5 from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:11:in `require'' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:11 from /usr/bin/gem:8:in `require'' from /usr/bin/gem:8 I have mysql-develop, the ruby dev and gcc installed> > -- > Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL:www.pobox.com/~tmz/pgp > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > A word to the wise ain''t necessary -- it''s the stupid ones who need > the advice. > -- Bill Cosby > > application_pgp-signature_part > < 1KViewDownload-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
This looks like you have a 32-bit Ruby and are trying to link to the 64-bit MySQL. On Mon, Oct 17, 2011 at 1:24 PM, robert.mortimer@gmail.com < robert.mortimer@gmail.com> wrote:> > > On Oct 17, 9:05 pm, Todd Zullinger <t...@pobox.com> wrote: > > robert.morti...@gmail.com wrote: > > > I am having no joy installing Puppet Server with MySQL support from > > > the EPEL on Centos 6. The active record support for MySQL seems to be > > > missing. Has anyone seen a good howto for this? > > > > Sadly, rubygem-rails is not built for EL-6. You can either rebuild > > the 2.3.8 packages from Fedora or find someone to act as a maintainer > > for these in EPEL. > > > But the puppet was from the epel, I sort of assumed it would have the > correct mysql > > When I attempt the gem install I get:- > > gem install mysql --with-mysql-include=/usr/include/mysql --with- > mysql-libs=/usr/lib64/mysql > /usr/lib/ruby/1.8/thread.so: /usr/lib/ruby/1.8/thread.so: wrong ELF > class: ELFCLASS32 - /usr/lib/ruby/1.8/thread.so (LoadError) > from /usr/lib/ruby/1.8/thread.rb:5 > from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:11:in `require'' > from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:11 > from /usr/bin/gem:8:in `require'' > from /usr/bin/gem:8 > > I have mysql-develop, the ruby dev and gcc installed > > > > > -- > > Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL:www.pobox.com/~tmz/pgp<http://www.pobox.com/%7Etmz/pgp> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > A word to the wise ain''t necessary -- it''s the stupid ones who need > > the advice. > > -- Bill Cosby > > > > application_pgp-signature_part > > < 1KViewDownload > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Oct 17, 9:26 pm, Russell Van Tassell <russel...@gmail.com> wrote:> This looks like you have a 32-bit Ruby and are trying to link to the 64-bit > MySQL. > > On Mon, Oct 17, 2011 at 1:24 PM, robert.morti...@gmail.com < >installed yum list | grep ruby ruby.x86_64 1.8.7.299-5.el6_0.1 @updates> > > > > > > robert.morti...@gmail.com> wrote: > > > On Oct 17, 9:05 pm, Todd Zullinger <t...@pobox.com> wrote: > > > robert.morti...@gmail.com wrote: > > > > I am having no joy installing Puppet Server with MySQL support from > > > > the EPEL on Centos 6. The active record support for MySQL seems to be > > > > missing. Has anyone seen a good howto for this? > > > > Sadly, rubygem-rails is not built for EL-6. You can either rebuild > > > the 2.3.8 packages from Fedora or find someone to act as a maintainer > > > for these in EPEL. > > > But the puppet was from the epel, I sort of assumed it would have the > > correct mysql > > > When I attempt the gem install I get:- > > > gem install mysql --with-mysql-include=/usr/include/mysql --with- > > mysql-libs=/usr/lib64/mysql > > /usr/lib/ruby/1.8/thread.so: /usr/lib/ruby/1.8/thread.so: wrong ELF > > class: ELFCLASS32 - /usr/lib/ruby/1.8/thread.so (LoadError) > > from /usr/lib/ruby/1.8/thread.rb:5 > > from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:11:in `require'' > > from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:11 > > from /usr/bin/gem:8:in `require'' > > from /usr/bin/gem:8 > > > I have mysql-develop, the ruby dev and gcc installed > > > > -- > > > Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL:www.pobox.com/~tmz/pgp<http://www.pobox.com/%7Etmz/pgp> > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > A word to the wise ain''t necessary -- it''s the stupid ones who need > > > the advice. > > > -- Bill Cosby > > > > application_pgp-signature_part > > > < 1KViewDownload > > > -- > > 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+unsubscribe@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/puppet-users?hl=en.-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
To be clear, the "Wrong Elf Class" error simply means that you are trying to mix 32 and 64 bit binaries... and the compiler isn''t going to allow that... so, look at Ruby and MySQL -- at least one of them is different. You can look at the file type by using "file" and the filename. For example, from a CentOS 6.x (32-bit/i686/i386) puppet host: $ file /usr/lib/ruby/1.8/thread.so /usr/lib/ruby/1.8/thread.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped $ file /usr/lib/mysql/libmysqlclient_r.so.16.0.0 /usr/lib/mysql/libmysqlclient_r.so.16.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped $ file `which ruby` /usr/bin/ruby: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped Hope that helps... Russell On Mon, Oct 17, 2011 at 1:42 PM, robert.mortimer@gmail.com < robert.mortimer@gmail.com> wrote:> > > On Oct 17, 9:26 pm, Russell Van Tassell <russel...@gmail.com> wrote: > > This looks like you have a 32-bit Ruby and are trying to link to the > 64-bit > > MySQL. > > > > On Mon, Oct 17, 2011 at 1:24 PM, robert.morti...@gmail.com < > > > installed > > yum list | grep ruby > ruby.x86_64 > 1.8.7.299-5.el6_0.1 @updates > > > > > > > > > > > > > > > robert.morti...@gmail.com> wrote: > > > > > On Oct 17, 9:05 pm, Todd Zullinger <t...@pobox.com> wrote: > > > > robert.morti...@gmail.com wrote: > > > > > I am having no joy installing Puppet Server with MySQL support from > > > > > the EPEL on Centos 6. The active record support for MySQL seems to > be > > > > > missing. Has anyone seen a good howto for this? > > > > > > Sadly, rubygem-rails is not built for EL-6. You can either rebuild > > > > the 2.3.8 packages from Fedora or find someone to act as a maintainer > > > > for these in EPEL. > > > > > But the puppet was from the epel, I sort of assumed it would have the > > > correct mysql > > > > > When I attempt the gem install I get:- > > > > > gem install mysql --with-mysql-include=/usr/include/mysql --with- > > > mysql-libs=/usr/lib64/mysql > > > /usr/lib/ruby/1.8/thread.so: /usr/lib/ruby/1.8/thread.so: wrong ELF > > > class: ELFCLASS32 - /usr/lib/ruby/1.8/thread.so (LoadError) > > > from /usr/lib/ruby/1.8/thread.rb:5 > > > from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:11:in `require'' > > > from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:11 > > > from /usr/bin/gem:8:in `require'' > > > from /usr/bin/gem:8 > > > > > I have mysql-develop, the ruby dev and gcc installed > > > > > > -- > > > > Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: > www.pobox.com/~tmz/pgp <http://www.pobox.com/%7Etmz/pgp>< > http://www.pobox.com/%7Etmz/pgp> > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > A word to the wise ain''t necessary -- it''s the stupid ones who need > > > > the advice. > > > > -- Bill Cosby > > > > > > application_pgp-signature_part > > > > < 1KViewDownload > > > > > -- > > > 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+unsubscribe@googlegroups.com. > > > For more options, visit this group at > > >http://groups.google.com/group/puppet-users?hl=en. > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Oct 17, 3:03 pm, Russell Van Tassell <russel...@gmail.com> wrote:> Personally, I''ve had better luck letting gem managed its own gems, rather > than depending on Yum repositories (specifically on CentOS). > > I''d take a list of the Ruby gems you''ve installed via rpm (rpm -q -a | grep > ruby) and then consider installing them directly, as so: > > % sudo gem install mysql > % sudo gem listI, on the other hand, would recommend avoiding gems altogether if you''re using the system''s Ruby (i.e. one you installed from an RPM, whether via yum or otherwise). Ruby modules installed via RPM are not (should not be) gems. Using both gem and rpm to manage the same Ruby installation is begging for trouble. John -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, Oct 18, 2011 at 6:19 AM, jcbollinger <John.Bollinger@stjude.org> wrote:> > > On Oct 17, 3:03 pm, Russell Van Tassell <russel...@gmail.com> wrote: >> Personally, I''ve had better luck letting gem managed its own gems, rather >> than depending on Yum repositories (specifically on CentOS). >> >> I''d take a list of the Ruby gems you''ve installed via rpm (rpm -q -a | grep >> ruby) and then consider installing them directly, as so: >> >> % sudo gem install mysql >> % sudo gem list > > > I, on the other hand, would recommend avoiding gems altogether if > you''re using the system''s Ruby (i.e. one you installed from an RPM, > whether via yum or otherwise). Ruby modules installed via RPM are not > (should not be) gems. Using both gem and rpm to manage the same Ruby > installation is begging for trouble.Why? The packages of many ruby libraries are basically gems wrapped in RPM. Basically it allows the library/tool to be registered with the RPM and gem database. I admit it''s not my favorite thing to have gems (and not RPMs), but technically there is almost nothing wrong with it, other than future RPMs can''t depend on something from a gem install only. There are plenty of other debates about rubygems, and whether or not they are useful or helpful or anything. But as far as having a system with ruby and using to gem to install things, it will work and is always all that bad.> > > John > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I''ve been working on building the Fedora 15 rails 3 RPMs for EL6. I''d be interested in doing that for EPEL, I''ll have to look into how to become a maintainer. On Oct 17, 4:05 pm, Todd Zullinger <t...@pobox.com> wrote:> robert.morti...@gmail.com wrote: > > I am having no joy installing Puppet Server with MySQL support from > > the EPEL on Centos 6. The active record support for MySQL seems to be > > missing. Has anyone seen a good howto for this? > > Sadly, rubygem-rails is not built for EL-6. You can either rebuild > the 2.3.8 packages from Fedora or find someone to act as a maintainer > for these in EPEL. > > -- > Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL:www.pobox.com/~tmz/pgp > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > A word to the wise ain''t necessary -- it''s the stupid ones who need > the advice. > -- Bill Cosby > > application_pgp-signature_part > < 1KViewDownload-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Oct 18, 2011, at 6:19 AM, jcbollinger wrote:> > > On Oct 17, 3:03 pm, Russell Van Tassell <russel...@gmail.com> wrote: >> Personally, I''ve had better luck letting gem managed its own gems, rather >> than depending on Yum repositories (specifically on CentOS). >> >> I''d take a list of the Ruby gems you''ve installed via rpm (rpm -q -a | grep >> ruby) and then consider installing them directly, as so: >> >> % sudo gem install mysql >> % sudo gem list > > > I, on the other hand, would recommend avoiding gems altogether if > you''re using the system''s Ruby (i.e. one you installed from an RPM, > whether via yum or otherwise). Ruby modules installed via RPM are not > (should not be) gems. Using both gem and rpm to manage the same Ruby > installation is begging for trouble.---- probably depends upon your ruby needs. If all you need is puppet then this might be reasonable but if you are actually doing anything else with ruby, you are going to need access to many gems that aren''t going to be available in rpm packages or like many other things with OS distribution packages, may be very outdated. The ruby community has been extremely active in solving the complexities involved in deploying all things ruby and things like bundler and gem clearly are more versatile on virtually every platform. Craig -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
It also depends on how many machines you''re managing. If you''ve got very many I''m with John: don''t cross the streams. It''s so easy to make RPMs from gems that there''s really no reason not to if you need a newer version than what''s provided. On Tue, Oct 18, 2011 at 10:14 AM, Craig White <craig.white@ttiltd.com> wrote:> > On Oct 18, 2011, at 6:19 AM, jcbollinger wrote: > >> >> >> On Oct 17, 3:03 pm, Russell Van Tassell <russel...@gmail.com> wrote: >>> Personally, I''ve had better luck letting gem managed its own gems, rather >>> than depending on Yum repositories (specifically on CentOS). >>> >>> I''d take a list of the Ruby gems you''ve installed via rpm (rpm -q -a | grep >>> ruby) and then consider installing them directly, as so: >>> >>> % sudo gem install mysql >>> % sudo gem list >> >> >> I, on the other hand, would recommend avoiding gems altogether if >> you''re using the system''s Ruby (i.e. one you installed from an RPM, >> whether via yum or otherwise). Ruby modules installed via RPM are not >> (should not be) gems. Using both gem and rpm to manage the same Ruby >> installation is begging for trouble. > ---- > probably depends upon your ruby needs. If all you need is puppet then this might be reasonable but if you are actually doing anything else with ruby, you are going to need access to many gems that aren''t going to be available in rpm packages or like many other things with OS distribution packages, may be very outdated. > > The ruby community has been extremely active in solving the complexities involved in deploying all things ruby and things like bundler and gem clearly are more versatile on virtually every platform. > > Craig > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
My worry is often that a poorly-crafted will overwrite something that the gem db expects to be there. It shouldn''t happen but it does - so for me I stick to all-RPMs, because at least then expectations are managed by the rpm database, and I can fix things by repairing a broken package. If gem and/or RPM break each other, there''s little I can do to fix it in any automated or predictable way. -Eric -- Eric Shamow Professional Services http://puppetlabs.com/ (c)631.871.6441 On Tuesday, October 18, 2011 at 12:43 PM, Michael Stahnke wrote:> On Tue, Oct 18, 2011 at 6:19 AM, jcbollinger <John.Bollinger@stjude.org (mailto:John.Bollinger@stjude.org)> wrote: > > > > > > On Oct 17, 3:03 pm, Russell Van Tassell <russel...@gmail.com (http://gmail.com)> wrote: > > > Personally, I''ve had better luck letting gem managed its own gems, rather > > > than depending on Yum repositories (specifically on CentOS). > > > > > > I''d take a list of the Ruby gems you''ve installed via rpm (rpm -q -a | grep > > > ruby) and then consider installing them directly, as so: > > > > > > % sudo gem install mysql > > > % sudo gem list > > > > > > I, on the other hand, would recommend avoiding gems altogether if > > you''re using the system''s Ruby (i.e. one you installed from an RPM, > > whether via yum or otherwise). Ruby modules installed via RPM are not > > (should not be) gems. Using both gem and rpm to manage the same Ruby > > installation is begging for trouble. > > Why? The packages of many ruby libraries are basically gems wrapped > in RPM. Basically it allows the library/tool to be registered with > the RPM and gem database. I admit it''s not my favorite thing to have > gems (and not RPMs), but technically there is almost nothing wrong > with it, other than future RPMs can''t depend on something from a gem > install only. > > There are plenty of other debates about rubygems, and whether or not > they are useful or helpful or anything. But as far as having a system > with ruby and using to gem to install things, it will work and is > always all that bad. > > > > > > John > > > > -- > > 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 (mailto:puppet-users@googlegroups.com). > > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com (mailto:puppet-users+unsubscribe@googlegroups.com). > > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > > -- > 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 (mailto:puppet-users@googlegroups.com). > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com (mailto:puppet-users+unsubscribe@googlegroups.com). > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, Oct 18, 2011 at 9:49 AM, Steve Snodgrass <pheran@gmail.com> wrote:> I''ve been working on building the Fedora 15 rails 3 RPMs for EL6. I''d > be interested in doing that for EPEL, I''ll have to look into how to > become a maintainer. >If you''re already in the Fedora/EPEL ecosystem, ping me in #epel. I can help. :) -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Oct 18, 11:43 am, Michael Stahnke <stah...@puppetlabs.com> wrote:> On Tue, Oct 18, 2011 at 6:19 AM, jcbollinger <John.Bollin...@stjude.org> wrote:[...]> > I, on the other hand, would recommend avoiding gems altogether if > > you''re using the system''s Ruby (i.e. one you installed from an RPM, > > whether via yum or otherwise). Ruby modules installed via RPM are not > > (should not be) gems. Using both gem and rpm to manage the same Ruby > > installation is begging for trouble. > > Why? The packages of many ruby libraries are basically gems wrapped > in RPM. Basically it allows the library/tool to be registered with > the RPM and gem database. I admit it''s not my favorite thing to have > gems (and not RPMs), but technically there is almost nothing wrong > with it, other than future RPMs can''t depend on something from a gem > install only.As others have described, if you use gems and RPMs on the same Ruby installation then you have two different sources of truth. They can and will disagree about what modules (to use a somewhat generic term) are installed. Their respective repositories can and will provide different versions of some modules, and different configurations of some other modules. Using both together on the same Ruby installation can and will make a hash of your Ruby library. Eventually. If you''re lucky, you''ll notice. Even RPMs registering their Ruby payloads with the gem database does not solve the problem, because gem is not so accommodating about synchronizing the RPM database. In any case, it is not safe to assume that *all* RPMs with Ruby payloads will install modules as gems.> There are plenty of other debates about rubygems, and whether or not > they are useful or helpful or anything. But as far as having a system > with ruby and using to gem to install things, it will work and is > always all that bad.Please don''t misunderstand: I have no particular complaint about gem itself. If you want all its gemtacular goodness then install a local Ruby build and go wild in it with gems. As long as you put it in a reasonable place (e.g. /usr/local) no RPM will touch it, so no problem. Of course, you have no obligation whatever to do as I advise. If you choose to use both gems and RPMs on the same Ruby then I wish you luck -- you''re a braver man than I. John -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, Oct 18, 2011 at 2:56 PM, jcbollinger <John.Bollinger@stjude.org> wrote:> > > On Oct 18, 11:43 am, Michael Stahnke <stah...@puppetlabs.com> wrote: >> On Tue, Oct 18, 2011 at 6:19 AM, jcbollinger <John.Bollin...@stjude.org> wrote: > [...] >> > I, on the other hand, would recommend avoiding gems altogether if >> > you''re using the system''s Ruby (i.e. one you installed from an RPM, >> > whether via yum or otherwise). Ruby modules installed via RPM are not >> > (should not be) gems. Using both gem and rpm to manage the same Ruby >> > installation is begging for trouble. >> >> Why? The packages of many ruby libraries are basically gems wrapped >> in RPM. Basically it allows the library/tool to be registered with >> the RPM and gem database. I admit it''s not my favorite thing to have >> gems (and not RPMs), but technically there is almost nothing wrong >> with it, other than future RPMs can''t depend on something from a gem >> install only. > > > As others have described, if you use gems and RPMs on the same Ruby > installation then you have two different sources of truth. They can > and will disagree about what modules (to use a somewhat generic term) > are installed. Their respective repositories can and will provide > different versions of some modules, and different configurations of > some other modules. Using both together on the same Ruby installation > can and will make a hash of your Ruby library. Eventually. If you''re > lucky, you''ll notice. > > Even RPMs registering their Ruby payloads with the gem database does > not solve the problem, because gem is not so accommodating about > synchronizing the RPM database. In any case, it is not safe to assume > that *all* RPMs with Ruby payloads will install modules as gems. > > >> There are plenty of other debates about rubygems, and whether or not >> they are useful or helpful or anything. But as far as having a system >> with ruby and using to gem to install things, it will work and is >> always all that bad. > > > Please don''t misunderstand: I have no particular complaint about gem > itself. If you want all its gemtacular goodness then install a local > Ruby build and go wild in it with gems. As long as you put it in a > reasonable place (e.g. /usr/local) no RPM will touch it, so no > problem. > > Of course, you have no obligation whatever to do as I advise. If you > choose to use both gems and RPMs on the same Ruby then I wish you luck > -- you''re a braver man than I. >I wasn''t really trying to disagree. Just that gem and rpm don''t have to fight too much. As an aside, I do maintain about 90 RPMs of gems in EPEL, so I totally understand having gems packaged when possible. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Why not use RVM ? It wll be easy to create a ruby env with its gems. It is in /usr/local and completely independant from the system ruby and all gems. I enforce not putting any files on the system which are not part of a RPM. For example, i use the puppetmaster and puppet rpms, so that both run and use the standard ruby 1.8.7 without any need of gem (i do not use mysql). But for the cloud provisioner that needs a lot of gems which do not exist as RPM, i put RVM and told it to have a ruby-1.8.7 with my needed gems. I put the default on rvm to keep using the default ruby, so that it will not impact on anything for my system, but i created a RVM wrapper for the second ruby, so that that i use this wrapper to run my puppet command when needing to do cloud actions. You could have a similar setup, but having your puppetmaster and puppet client using the rvm wrapped ruby and gems (eg the mysql gem), and you will not have to worry about trashing your system with files not part of RPMs I have a Puppet recipe to install rvm, manage rubies, gems, etc... Tell me if you are interested, i could post it On 18 oct, 23:56, jcbollinger <John.Bollin...@stJude.org> wrote:> On Oct 18, 11:43 am, Michael Stahnke <stah...@puppetlabs.com> wrote: > > > On Tue, Oct 18, 2011 at 6:19 AM, jcbollinger <John.Bollin...@stjude.org> wrote: > [...] > > > I, on the other hand, would recommend avoiding gems altogether if > > > you''re using the system''s Ruby (i.e. one you installed from an RPM, > > > whether via yum or otherwise). Ruby modules installed via RPM are not > > > (should not be) gems. Using both gem and rpm to manage the same Ruby > > > installation is begging for trouble. > > > Why? The packages of many ruby libraries are basically gems wrapped > > in RPM. Basically it allows the library/tool to be registered with > > the RPM and gem database. I admit it''s not my favorite thing to have > > gems (and not RPMs), but technically there is almost nothing wrong > > with it, other than future RPMs can''t depend on something from a gem > > install only. > > As others have described, if you use gems and RPMs on the same Ruby > installation then you have two different sources of truth. They can > and will disagree about what modules (to use a somewhat generic term) > are installed. Their respective repositories can and will provide > different versions of some modules, and different configurations of > some other modules. Using both together on the same Ruby installation > can and will make a hash of your Ruby library. Eventually. If you''re > lucky, you''ll notice. > > Even RPMs registering their Ruby payloads with the gem database does > not solve the problem, because gem is not so accommodating about > synchronizing the RPM database. In any case, it is not safe to assume > that *all* RPMs with Ruby payloads will install modules as gems. > > > There are plenty of other debates about rubygems, and whether or not > > they are useful or helpful or anything. But as far as having a system > > with ruby and using to gem to install things, it will work and is > > always all that bad. > > Please don''t misunderstand: I have no particular complaint about gem > itself. If you want all its gemtacular goodness then install a local > Ruby build and go wild in it with gems. As long as you put it in a > reasonable place (e.g. /usr/local) no RPM will touch it, so no > problem. > > Of course, you have no obligation whatever to do as I advise. If you > choose to use both gems and RPMs on the same Ruby then I wish you luck > -- you''re a braver man than I. > > John-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Why not use RVM ? It wll be easy to create a ruby env with its gems. It is in /usr/local and completely independant from the system ruby and all gems. I enforce not putting any files on the system which are not part of a RPM. For example, i use the puppetmaster and puppet rpms, so that both run and use the standard ruby 1.8.7 without any need of gem (i do not use mysql). But for the cloud provisioner that needs a lot of gems which do not exist as RPM, i put RVM and told it to have a ruby-1.8.7 with my needed gems. I put the default on rvm to keep using the default ruby, so that it will not impact on anything for my system, but i created a RVM wrapper for the second ruby, so that that i use this wrapper to run my puppet command when needing to do cloud actions. You could have a similar setup, but having your puppetmaster and puppet client using the rvm wrapped ruby and gems (eg the mysql gem), and you will not have to worry about trashing your system with files not part of RPMs I have a Puppet recipe to install rvm, manage rubies, gems, etc... Tell me if you are interested, i could post it On 18 oct, 23:56, jcbollinger <John.Bollin...@stJude.org> wrote:> On Oct 18, 11:43 am, Michael Stahnke <stah...@puppetlabs.com> wrote: > > > On Tue, Oct 18, 2011 at 6:19 AM, jcbollinger <John.Bollin...@stjude.org> wrote: > [...] > > > I, on the other hand, would recommend avoiding gems altogether if > > > you''re using the system''s Ruby (i.e. one you installed from an RPM, > > > whether via yum or otherwise). Ruby modules installed via RPM are not > > > (should not be) gems. Using both gem and rpm to manage the same Ruby > > > installation is begging for trouble. > > > Why? The packages of many ruby libraries are basically gems wrapped > > in RPM. Basically it allows the library/tool to be registered with > > the RPM and gem database. I admit it''s not my favorite thing to have > > gems (and not RPMs), but technically there is almost nothing wrong > > with it, other than future RPMs can''t depend on something from a gem > > install only. > > As others have described, if you use gems and RPMs on the same Ruby > installation then you have two different sources of truth. They can > and will disagree about what modules (to use a somewhat generic term) > are installed. Their respective repositories can and will provide > different versions of some modules, and different configurations of > some other modules. Using both together on the same Ruby installation > can and will make a hash of your Ruby library. Eventually. If you''re > lucky, you''ll notice. > > Even RPMs registering their Ruby payloads with the gem database does > not solve the problem, because gem is not so accommodating about > synchronizing the RPM database. In any case, it is not safe to assume > that *all* RPMs with Ruby payloads will install modules as gems. > > > There are plenty of other debates about rubygems, and whether or not > > they are useful or helpful or anything. But as far as having a system > > with ruby and using to gem to install things, it will work and is > > always all that bad. > > Please don''t misunderstand: I have no particular complaint about gem > itself. If you want all its gemtacular goodness then install a local > Ruby build and go wild in it with gems. As long as you put it in a > reasonable place (e.g. /usr/local) no RPM will touch it, so no > problem. > > Of course, you have no obligation whatever to do as I advise. If you > choose to use both gems and RPMs on the same Ruby then I wish you luck > -- you''re a braver man than I. > > John-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I got it installed in the end: 1) Only install dev libraries for the architecture you are using (gcc and mysql dev) 2) Gems from source (not RPM) were used 3) Active record can not be the latest version (down grade was required) The only other option is to roll your own RPM or scavenge them from elsewhere on the net. As that can screw up the whole OS update I would avoid it unless you have a development environment and lots of time. It is not ideal and I do feel that if puppet is in the EPEL then the required ruby dependencies should be there but I only run one puppet server and a moderate number of clients so this is not a project I would take on. My contribution when I get a moment will be a how-to to prevent someone else going through my pain <SOLVED> On 19 October 2011 11:21, Alexandre <alexandre.fouche@gmail.com> wrote:> Why not use RVM ? It wll be easy to create a ruby env with its gems. > It is in /usr/local and completely independant from the system ruby > and all gems. I enforce not putting any files on the system which are > not part of a RPM. > > For example, i use the puppetmaster and puppet rpms, so that both run > and use the standard ruby 1.8.7 without any need of gem (i do not use > mysql). But for the cloud provisioner that needs a lot of gems which > do not exist as RPM, i put RVM and told it to have a ruby-1.8.7 with > my needed gems. I put the default on rvm to keep using the default > ruby, so that it will not impact on anything for my system, but i > created a RVM wrapper for the second ruby, so that that i use this > wrapper to run my puppet command when needing to do cloud actions. > > You could have a similar setup, but having your puppetmaster and > puppet client using the rvm wrapped ruby and gems (eg the mysql gem), > and you will not have to worry about trashing your system with files > not part of RPMs > > I have a Puppet recipe to install rvm, manage rubies, gems, etc... > Tell me if you are interested, i could post it > > > On 18 oct, 23:56, jcbollinger <John.Bollin...@stJude.org> wrote: >> On Oct 18, 11:43 am, Michael Stahnke <stah...@puppetlabs.com> wrote: >> >> > On Tue, Oct 18, 2011 at 6:19 AM, jcbollinger <John.Bollin...@stjude.org> wrote: >> [...] >> > > I, on the other hand, would recommend avoiding gems altogether if >> > > you''re using the system''s Ruby (i.e. one you installed from an RPM, >> > > whether via yum or otherwise). Ruby modules installed via RPM are not >> > > (should not be) gems. Using both gem and rpm to manage the same Ruby >> > > installation is begging for trouble. >> >> > Why? The packages of many ruby libraries are basically gems wrapped >> > in RPM. Basically it allows the library/tool to be registered with >> > the RPM and gem database. I admit it''s not my favorite thing to have >> > gems (and not RPMs), but technically there is almost nothing wrong >> > with it, other than future RPMs can''t depend on something from a gem >> > install only. >> >> As others have described, if you use gems and RPMs on the same Ruby >> installation then you have two different sources of truth. They can >> and will disagree about what modules (to use a somewhat generic term) >> are installed. Their respective repositories can and will provide >> different versions of some modules, and different configurations of >> some other modules. Using both together on the same Ruby installation >> can and will make a hash of your Ruby library. Eventually. If you''re >> lucky, you''ll notice. >> >> Even RPMs registering their Ruby payloads with the gem database does >> not solve the problem, because gem is not so accommodating about >> synchronizing the RPM database. In any case, it is not safe to assume >> that *all* RPMs with Ruby payloads will install modules as gems. >> >> > There are plenty of other debates about rubygems, and whether or not >> > they are useful or helpful or anything. But as far as having a system >> > with ruby and using to gem to install things, it will work and is >> > always all that bad. >> >> Please don''t misunderstand: I have no particular complaint about gem >> itself. If you want all its gemtacular goodness then install a local >> Ruby build and go wild in it with gems. As long as you put it in a >> reasonable place (e.g. /usr/local) no RPM will touch it, so no >> problem. >> >> Of course, you have no obligation whatever to do as I advise. If you >> choose to use both gems and RPMs on the same Ruby then I wish you luck >> -- you''re a braver man than I. >> >> John > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi trey, I put it here: https://github.com/alexfouche/rvm On 19 oct, 21:07, Robert Mortimer <robert.morti...@gmail.com> wrote:> I got it installed in the end: > > 1) Only install dev libraries for the architecture you are using (gcc > and mysql dev) > 2) Gems from source (not RPM) were used > 3) Active record can not be the latest version (down grade was required) > > The only other option is to roll your own RPM or scavenge them from > elsewhere on the net. As that can screw up the whole OS update I would > avoid it unless you have a development environment and lots of time. > It is not ideal and I do feel that if puppet is in the EPEL then the > required ruby dependencies should be there but I only run one puppet > server and a moderate number of clients so this is not a project I > would take on. > > My contribution when I get a moment will be a how-to to prevent > someone else going through my pain > > <SOLVED> > > On 19 October 2011 11:21, Alexandre <alexandre.fou...@gmail.com> wrote: > > > > > > > > > Why not use RVM ? It wll be easy to create a ruby env with its gems. > > It is in /usr/local and completely independant from the system ruby > > and all gems. I enforce not putting any files on the system which are > > not part of a RPM. > > > For example, i use the puppetmaster and puppet rpms, so that both run > > and use the standard ruby 1.8.7 without any need of gem (i do not use > > mysql). But for the cloud provisioner that needs a lot of gems which > > do not exist as RPM, i put RVM and told it to have a ruby-1.8.7 with > > my needed gems. I put the default on rvm to keep using the default > > ruby, so that it will not impact on anything for my system, but i > > created a RVM wrapper for the second ruby, so that that i use this > > wrapper to run my puppet command when needing to do cloud actions. > > > You could have a similar setup, but having your puppetmaster and > > puppet client using the rvm wrapped ruby and gems (eg the mysql gem), > > and you will not have to worry about trashing your system with files > > not part of RPMs > > > I have a Puppet recipe to install rvm, manage rubies, gems, etc... > > Tell me if you are interested, i could post it > > > On 18 oct, 23:56, jcbollinger <John.Bollin...@stJude.org> wrote: > >> On Oct 18, 11:43 am, Michael Stahnke <stah...@puppetlabs.com> wrote: > > >> > On Tue, Oct 18, 2011 at 6:19 AM, jcbollinger <John.Bollin...@stjude.org> wrote: > >> [...] > >> > > I, on the other hand, would recommend avoiding gems altogether if > >> > > you''re using the system''s Ruby (i.e. one you installed from an RPM, > >> > > whether via yum or otherwise). Ruby modules installed via RPM are not > >> > > (should not be) gems. Using both gem and rpm to manage the same Ruby > >> > > installation is begging for trouble. > > >> > Why? The packages of many ruby libraries are basically gems wrapped > >> > in RPM. Basically it allows the library/tool to be registered with > >> > the RPM and gem database. I admit it''s not my favorite thing to have > >> > gems (and not RPMs), but technically there is almost nothing wrong > >> > with it, other than future RPMs can''t depend on something from a gem > >> > install only. > > >> As others have described, if you use gems and RPMs on the same Ruby > >> installation then you have two different sources of truth. They can > >> and will disagree about what modules (to use a somewhat generic term) > >> are installed. Their respective repositories can and will provide > >> different versions of some modules, and different configurations of > >> some other modules. Using both together on the same Ruby installation > >> can and will make a hash of your Ruby library. Eventually. If you''re > >> lucky, you''ll notice. > > >> Even RPMs registering their Ruby payloads with the gem database does > >> not solve the problem, because gem is not so accommodating about > >> synchronizing the RPM database. In any case, it is not safe to assume > >> that *all* RPMs with Ruby payloads will install modules as gems. > > >> > There are plenty of other debates about rubygems, and whether or not > >> > they are useful or helpful or anything. But as far as having a system > >> > with ruby and using to gem to install things, it will work and is > >> > always all that bad. > > >> Please don''t misunderstand: I have no particular complaint about gem > >> itself. If you want all its gemtacular goodness then install a local > >> Ruby build and go wild in it with gems. As long as you put it in a > >> reasonable place (e.g. /usr/local) no RPM will touch it, so no > >> problem. > > >> Of course, you have no obligation whatever to do as I advise. If you > >> choose to use both gems and RPMs on the same Ruby then I wish you luck > >> -- you''re a braver man than I. > > >> John > > > -- > > 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+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.