William Nagel wrote:
>> Make ./trunk, ./branches, and ./tags REQUIRED subdirectories, not
>> just "best practices". [Is it too late for this?!!!]
>>
>> These directories are automatically created when the repository is
>> created. [Does this reduce flexibility too much?]
>
>
> ...If the organization is forced, all of that flexibility goes away.
A number of people have presented arguments that all boil down to "don't
force people to do it this way."
I must point out what should be obvious, which is that automatically
providing these directories doesn't force anybody to actually use them.
I didn't see anything in the suggestion that would remove a single bit
of existing functionality. Just to distinguish the directories, I'd be
tempted to name them .trunk, .branches and .tags, and think through the
implications, along the lines of the way the UNIX ls command and similar
treat leading periods on file names. But that would make it clearer
that these are merely being made available, not being forced.
However, a counterpoint to this is that there's nothing preventing
anyone from implementing this as a layer on top of svn. In other words,
write an installation package that takes a standard svn kit and sets it
up with these directories, and with appropriate hooks in place to
control their usage. So I really don't see much point in beating this
issue to death.
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 23 23:40:42 2004