David Corley wrote:
> Hey all,
> We've just implemented Subversion at our workplace, and after getting
> everything running well together we ran into an odd problem last week.
> One of our less experience team members inadvertently created an
> svn:externals reference on a directory to a higher-level directory in
> the same repository. This had the unfortunate effect of infinite
> recursion on the directory, which in turn made updating difficult to say
> the least.
> My multi-part question is:
> 1. Does a subversion working copy contain the reference to the
> repository where it was checked-out from?
> 2. Assuming 1) is true, are there valid reasons why SVN would allow a
> repo to have an svn:external reference to itself?
> 3. Assuming 2) is false, is there a design case for some sort of check
> on the svn:external property to ensure it doesn't reference the current
> WRT to 1), I'm guessing the alternative is that the SVN client rather
> than the working copy retains the reference to the repo.
> WRT to 3), There's only a major issue if the svn:external property
> references a directory higher in the hierarchy than that which has the
> svn:external property, which causes the infinite recursion.
> I'll welcome any comments on the issue.
I gave this a dime of my time and figured that you'd get a
similar problem with two (or more) repositories that cross
reference each other using svn:external. The only possible
solution I can see would be for the client checkout code to
handle this (if at all possible).
P.s. Dave, I'm sorry for the double posting.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-27 16:44:04 CET