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