Issue #7788 has been updated by Jan Ivar Beddari.
I'd like to see this happen aswell. Could it be done by creating Puppet-instance-specific paths using modules? http://janveldeman.wordpress.com/2008/04/14/project-specific-rubygems/ Probably not the most elegant solution. Or a config setting with an explanation? In my (albeit small) Puppet kingdom catering for the dual install case seems less useful than this. ---------------------------------------- Feature #7788: Puppet should allow rubygems to deliver new functionality https://projects.puppetlabs.com/issues/7788 Author: R.I. Pienaar Status: Code Insufficient Priority: Normal Assignee: Nigel Kersten Category: plug-ins Target version: 2.7.x Affected Puppet version: Keywords: Branch: ripienaar/feature/master/7788 It would be desirable to use Rubygems to install things like parser functions. There might be cases where you only want a function on the master, pluginsync would copy it everywhere and everywhere might not have the dependencies needed to run it. If the autoloader considered the rubygem search path while autoloading this should allow gems to extend puppet. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
