On Thu, Jun 16, 2011 at 1:59 PM, Gabriel Filion <lelu...@gmail.com> wrote:
> On 11-06-16 03:47 PM, Nathan Clemons wrote: > > Or what you might want to do is to create a specific common directory > > for code that should be shared, and per-environment directories which > > contain code that should not be shared. If you find that something > > should no longer be common, you then move it into the per-env > > directories as appropriate. > > Oh ok ... I'll have to work something out then.. this is more > complicated to use than I thought. > This shouldn't be that complicated. Do you have modules with the same name in multiple modulepath components? If not, then you should be seeing the behavior you're expecting. 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. -- 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.
