I would have assumed that you'd always want to qualify the module
names as the best practise. Collisions in namespaces wreak havoc in
many other domains. I'm thinking of Java class names being bound to
domain names as an approach that works elsewhere.
Am I being naive?
Best
Julian
2009/9/17 Peter Meier <peter.me...@immerda.ch>:
>
> Hi
>
>> I think that would be terrible. Having two different paths for the
>> same namespace is confusing and will easily lead to problems.
>
> yeah I feel more this way as well.
>
>> However, the example you give is correct: you can't have the same
>> module name in two modulepaths and usually want to prefix the
>> classnames to avoid name collisions.
>
> so for the Best Practises:
>
> If we do multiple sources for a file (and I do that a lot, as it makes
> puppet so flexible) what would you prefer?
>
> in module foobar and the 0.25 way:
>
> file{'/tmp/a':
> source => [ "puppet:///files/foobar/${fqdn}/a",
> "puppet:///files/foobar/a",
> "puppet:///modules/foobar/${operatingsystem}/a",
> "puppet:///modules/foobar/a" ],
> }
>
> or
>
> file{'/tmp/a':
> source => [ "puppet:///modules/site-foobar/${fqdn}/a",
> "puppet:///modules/site-foobar/a",
> "puppet:///modules/foobar/${operatingsystem}/a",
> "puppet:///modules/foobar/a" ],
> }
>
> ???
>
> cheers pete
>
> >
>
--
Julian Simpson
Software Build and Deployment
http://www.build-doctor.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
