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.bollin...@stjude.org > (mailto:john.bollin...@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+unsubscr...@googlegroups.com > > (mailto:puppet-users+unsubscr...@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+unsubscr...@googlegroups.com > (mailto:puppet-users+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
