Moritz Lenz wrote:
Darren Duncan wrote:
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.
Yes, I considered that option (and stated it), and its better than nothing, but
I thought there had to be a better way, since conceivably the :auth is "who
released it", and the branch thing I was talking about seemed conceivably different.
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.
I agree that having arbitrary attributes here does look like over-engineering
and an ideal situation may be simpler.
On the other hand, what you describe might actually be the best, and might be
technically simplest in some respects and most adaptable. After all, someone
else may realize another class of scenarios not previously thought about, like I
suspect is the case with my 'branch' option.
But arbitrary-attributes runs the risk of creating its own problems when anybody
takes advantage of it in their own way; we still need some standards.
-- Darren Duncan
