Ronald Cannes wrote:
>> Subversion already provides this
>> infrastructure, and any admin worth his paycheck should be able to
>> easily write a couple of scripts to make his/her life easier in this
>> way.
>
> Again, scripts isn't the answer. The first thing my programmers will ask
> when we are done migrating from other SCM's is "how do I pick the
> repository." They expect, say, TortoiseSVN or at least the svn client to
> provide a list of repositories. But there is no such thing... Sad,
> especially since repos-names are case sensitive :-(
Why are scripts not the answer?
The answer to "how do I pick the repository" is "you include it in the URL
you access".
You have made it clear that subversion handles repository recovery
differently to what you and your programmers are used to. You haven't made
it clear why this is a bad thing.
Perhaps it would help people here understand why you think this is such a
core feature, if you posted a link to the relevant part of some online
documentation for these "other SCM's".
Please also explain why a simple HTML page listing repositories is not a
solution for you.
Also, bear in mind that Subversion's goal, at least for 1.0, is to become "a
compelling replacement for CVS". CVS does not provide automatic repository
listing - do you believe that specific lack has hindered the use of CVS?
Also, if you are still not convinced that this feature is impossible within
the current architecture of subversion, then re-read Ben Collins-Sussman's
most-recent 2 emails.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 11 18:11:12 2003