On Fri, 2006-11-17 at 12:40 +1300, Talden wrote:
> If I'm in folder /work/wc/proja_trunk/src/com/fiddle/dee/d
>
> and I do "svn update"
>
> where does it look? How does svn know which of the parent folders is
> the one with the svn data without opening each folder and listing the
> contents to discover where the svn data is.
>
> There are solutions for this of course. You could have the client
> have a standard location within which it keeps stores of data for each
> working copy but...
>
> You give up the ability to treat each folder of a working copy as an
> enclosed working copy... You would no longer just be able to locally
> clone a working copy or trim it down. What I'm saying (and what I'm
> hearing from others) is that there is no simple solution that resolves
> this issue without giving up a lot of existing functionality.
What if:
All instances of the .svn directory could be replaced by a
file containing the (preferably absolute) path to the real directory
to use? Then you'd just need something to create new ones
as needed based on either the one in the directory where a
new subdirectory is being added or for the top level, a command
line or environment setting. Then internally, subversion could
treat these like symlinks with the advantage that to everything
else it is just a file. You'd probably only use this option in
situations where a real .svn directory would cause trouble, and
the only thing I can think of that you would lose is the ability
to move all or part of the tree to a place (like a different host)
where the path reference didn't work. In that case you could just
check out a new copy where you want it anyway.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 01:14:05 2006