Issue #3789 has been updated by Nigel Kersten.
Is there really such a thing as "the module path" for those of us using environments? We've explicitly not defined a default module path entirely to cope with malformed client environment names. Also, I'm not so sure modules are so inert that we can happily copy them in and be satisfied they have no effect on the system. If we have internal imports, or definitions won't they get read anyway? If you have a lib/facter module sub-directory, won't that pluginsync to the clients simply by virtue of being in a modulepath regardless of whether or not you're including the module? ---------------------------------------- Feature #3789: Tool should install into module path directly rather than make user add module to path http://projects.puppetlabs.com/issues/3789 Author: James Turnbull Status: Needs more information Priority: Normal Assigned to: Igal Koshevoy Category: module tool Target version: Keywords: Branch: -- 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.
