Darren Duncan wrote: > In regards to http://perlcabal.org/syn/S11.html#Versioning I have recently > considered that it may be deficient in addressing a possibly-common > situation, > and I'm looking for input on how to handle that situation, either for a best > practice that works within the current model, or on enhancements to the > versioning spec to better handle it. > > For background, right now there are mainly 3 parts to a module name (I'm > ignoring "from" for the moment), which are "name", "auth", "ver", where each > part of the sequence is evaluated in the context of the parts before it. > > Now the purpose of "auth" is to distinguish between different > entities/authorities/authors that release a version of Perl or a Perl module, > and "ver" is the sequential numbering scheme where each "auth" has its own. > > The question I have is what to do when a single same authority wants to > release > multiple forks or branches of the same module,
It splits up into multiple authorities, conceptually. For example for the development branches for perl5 one could write :auth<perl.org:v5.8> and :aut<perl.org:v5.10>, and be happy, I know this is hijacking the concept a bit, but it should work fine. If that's not enough for you, maybe we could generalize the long name to include arbitrary attributes that must match, but I fear over-engineering here. Cheers, Moritz
