Trevor --
> How does this work in the case of multi-party development?
>
> For instance, you now have the Module Forge (woo), but I'm sure you're
> going to get two modules with a 'service { "mysql"' or somesuch.
>
> I know that it's easy to say "just be careful", but throwing up the
> overworked puny human SA defense, not conflicting on duplicate names
> is going to cause a massive amount of headache in my opinion.
>
> How else could this be solved so that people are not bitten by
> conflicts? Warnings perhaps?
I'm not sure I'm seeing the problem you are worried about.
The feature we're planning on implementing is very targeted at a
specific class of use cases: places where the natural title of a
resource actually contains two or more pieces of data, such as an MS
Win file path "C:/foo" which contains both a traditional path and a
"drive letter." The idea is to let the user specify these in the
natural way and parse them to get the individual fields which
(collectively) would be the unique identifier for the resource.
Thus you could have "C:/foo" and "D:/foo" and "C:/bar", etc. so long
as there was only one occurrence of each {drive_letter, path}
combination.
I'm not seeing the multi-party development issue here.
-- Markus
-----------------------------------------------------------
The power of accurate observation is
commonly called cynicism by those
who have not got it. ~George Bernard Shaw
------------------------------------------------------------
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" 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-dev?hl=en.
