[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [BUG] The client can't use a different directory than .svn

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2003-12-10 05:02:04 CET

I've looked into this and it doesn't look like it will be fixed any time
soon for VS 2003. However, it also doesn't look like it will be a problem
with the next version of VS (not that it really helps people right now).

 Kevin Pilch-Bisson
> -----Original Message-----
> From: D.J. Heap [mailto:dj@shadyvale.net]
> Sent: Tuesday, December 09, 2003 4:47 PM
> To: Kevin Pilch-Bisson
> Cc: 'Branko Cibej'; 'Lübbe Onken'; dev@subversion.tigris.org
> Subject: Re: [BUG] The client can't use a different directory than .svn
> Kevin Pilch-Bisson wrote:
> >
> >>-----Original Message-----
> >>From: Branko Cibej [mailto:brane@xbc.nu]
> >>Sent: Tuesday, December 09, 2003 11:25 AM
> >>To: Lübbe Onken
> >>Cc: dev@subversion.tigris.org
> >>Subject: Re: [BUG] The client can't use a different directory than .svn
> >
> >
> > <snip>
> >
> >>It would also break our WC portability mini-feature (not sure how
> >>interesting that is, though)
> >
> >
> > How does that work w.r.t. eol-style:native files right now?  Do we even
> have
> > this mini-feature in the presence of eol-style:native?
> >
> > <snip>
> >
> >>(On the other hand, it's a pity we didn't notice this ASP.NET/IIS
> >>brokenness a year ago)
> >>
> >
> >
> > I'm trying to look into this more.
> >
> > What sequence of steps (and what versions of software), does this not
> work
> > with?
> >
> >
> > -- Kevin
> The root of the problem is that IIS will show you .svn directories, but
>   refuses to let you into them.  VSNet tries to enumerate files and
> directories in web projects (through IIS) and dies when it gets to .svn
> directories.
> I looked at this a while ago as I knew we were going to hit it -- and we
> are running into it regularly now.  The previous thread ended (I think)
> with the possibility of a patch being accepted (at least reviewed and
> considered) if it enabled the client to handle either a '.svn' or a
> '_svn' admin diretory name, and then create new admin directories with
> the platform's preferred name.
> The key function is v_extend_with_adm_name in libsvn_wc/adm_files.c, I
> believe.  However, this seems to be a heavily used function and putting
> a check for the current admin dir name (potentially two checks) every
> time it is called seemed like it could be expensive unless some caching
> was done or something (perhaps I'm missing something obvious, of
> course).  I haven't had time to pursue it further than this brief
> analyses, though.
> Just changing the #define on Windows works, but breaks old working
> copies (if no other work is done to upgrade them) and prevents them from
> being used on other OS', although the utility of that is questionable it
> sounds like.
> Also, for what it's worth, I would prefer '_svn' to just 'svn' if it
> comes to renaming the admin dir.  Mostly just because it sorts
> nicer...no really strong feelings, though.
> DJ
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 10 05:03:04 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.