Login | Register
My pages Projects Community openCollabNet

Discussions > users [DISABLED] > Re: Not a bug, but a subversion design issue that perhaps needs addressing......comments please

subversion
Discussion topic

Back to topic list

Re: Not a bug, but a subversion design issue that perhaps needs addressing......comments please

Author Daniel Widenfalk <Daniel dot Widenfalk at iar dot se>
Full name Daniel Widenfalk <Daniel dot Widenfalk at iar dot se>
Date 2009-10-27 08:35:15 PDT
Message 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
> repository?
>
> 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.
>
> Regards,
> Dave

Hi all,

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).

Regards
/Daniel Widenfalk

P.s. Dave, I'm sorry for the double posting.

« Previous message in topic | 2 of 8 | Next message in topic »

Messages

Show all messages in topic

Not a bug, but a subversion design issue that perhaps needs addressing......comments please David Corley <davidcorley at gmail dot com> David Corley <davidcorley at gmail dot com> 2009-10-27 08:22:23 PDT
     Re: Not a bug, but a subversion design issue that perhaps needs addressing......comments please Daniel Widenfalk <Daniel dot Widenfalk at iar dot se> Daniel Widenfalk <Daniel dot Widenfalk at iar dot se> 2009-10-27 08:35:15 PDT
         Re: Not a bug, but a subversion design issue that perhaps needs addressing......comments please nick_stolwijk Nick Stolwijk 2009-10-27 08:50:30 PDT
         Re: Not a bug, but a subversion design issue that perhaps needs addressing......comments please hwright Hyrum K. Wright 2009-10-27 08:49:58 PDT
             Re: Not a bug, but a subversion design issue that perhaps needs addressing......comments please Alfred Perlstein <bright at mu dot org> Alfred Perlstein <bright at mu dot org> 2009-11-08 10:14:36 PST
     Re: Not a bug, but a subversion design issue that perhaps needs addressing......comments please David Corley <davidcorley at gmail dot com> David Corley <davidcorley at gmail dot com> 2009-10-27 08:40:06 PDT
         Re: Not a bug, but a subversion design issue that perhaps needs addressing......comments please Daniel Widenfalk <Daniel dot Widenfalk at iar dot se> Daniel Widenfalk <Daniel dot Widenfalk at iar dot se> 2009-10-27 08:52:59 PDT
     Re: Not a bug, but a subversion design issue that perhaps needs addressing......comments please mikedixon Mike Dixon 2009-10-27 10:31:42 PDT
Messages per page: