Giovanni Bajo wrote:
> If you did not read the document, how can you know that the tool is too
> specific? In my opinion, it allows to do all the common operations needed to
> handle vendor branches. I would be pleased if you could show me a specific
> usage case which the tool is not able to cover. In fact, it automates the
> usage pattern of vendor branches described in the SVN book too.
I did read the document, just not at the level required to consider all
of the implementation details. You can accuse me of a drive-by review,
to which I would gladly admit to. I'll try to go through in more detail
now, but my gut instinct is that you have already chosen the means that
you want to use to solve your "problem" without having spent enough time
defining the "problem" you want to solve.
You are trying to hide the implementation details from the user, which
very much goes against the grain of the Subversion core. In particular
"Implicit URLs" make some huge leaps of faith about the repository
layout which just isn't true for many sites. You have chosen two common
layouts and tried to hide the details in a new configuration file. Your
proposal is not extensible, however.
You've spent a fair amount of time coming up with the commandline
invocations, but it doesn't seem like much time in considering the
implementation details. For a simple example, some external library use
versions ala 1.23 and others user 1.2.3; how are you going to determine
which is the "latest" vendor branch?
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 19 19:50:07 2006