On 06/17/2011 10:52 AM, Nigel Kersten wrote:
It's not entirely unreasonable to expect that if module 'foo' is found in one modulepath component, that no other module named 'foo' should come into play, but I think we have some edge cases here. Please feel free to file a feature request around modulepath behaving more like $PATH in the shell does.
I actually played around with this for a while, trying to come up with a scheme for stackable configurations. The hack needed to make it work is to install links higher in the stack to files lower in the stack, because where ever puppet finds a module in the stack of modules trees, that module tree is where it looks for all the other related files. It will not drill down through the stack ('path') for each file of
the module. Nor would you want it to. Anyway, it ended up ugly, and I went looking for a better way. -- vagn -- 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.
