Issue #7788 has been updated by Jeff McCune.
On Mon, Jun 6, 2011 at 4:25 PM, <[email protected]> wrote: > Two, we are concerned that this potentially adds trouble when someone has > two copies of Puppet installed, one through RubyGems, and the other through > an OS package, or from source, or something like that. This introduces a new > path that code can get loaded, and it isn’t at all clear which will win from > the outside. > This is already an issue today; people can't have two versions of Puppet that exist in different parts of the $LOAD_PATH. It has been for a long time, so I don't think this is a new concern, just a long standing old concern. =) The answer is that they both win. You get types loaded from the "other" version and they fight each other. -Jeff ---------------------------------------- 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.
