If there were a standard shared location, that would be an option. Debian has moved along those lines (a shared vendor_ruby that both ruby 1.8 and ruby 1.9 load from), but for EL and Fedora currently, that doesn't exist. And without knowing which ruby 1.9 is being built against, it is impossible to guess what the libdir layout would look like.
On Mon, Oct 1, 2012 at 4:36 PM, Jeff McCune <j...@puppetlabs.com> wrote: > On Mon, Oct 1, 2012 at 1:49 PM, Matthaus Owens <matth...@puppetlabs.com> > wrote: >> The builds of puppet require ruby, but are built with ruby 1.8, 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 what is in epel. If >> there is ever a ruby 1.9 package in those repos, we will certainly >> look at building puppet 3.x to support it. In the meantime, you can >> rebuild the puppet 3.0.0 source rpm against your ruby package and as >> long as it defines the sitelibdir to be in your ruby 1.9's load path, >> it should work just fine. You would also need to rebuild the facter >> and hiera rpms in the same way for puppet to find them in its load >> path. > > Is it a viable option to change the official RPM's to install Puppet > into a location that could be shared by multiple ruby interpreters? > Perhaps as a gem where two different ruby installations share a common > element along the GEM_PATH? > > -Jeff -- Matthaus Owens Release Manager, Puppet Labs -- 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.
