Thanks for the reply.
I'd think that junctions/symlinks (and hardlinks) are supposed to be
totally transparent to applications (ie looking, acting and smelling
like a real directory), so this is not the behaviour i expect.
Could there be a reason svn does this on purpose? I can't think of one.
TIA,
Wouter
On 07/02/2008, Erik Huelsmann <ehuels_at_gmail.com> wrote:
> On Feb 6, 2008 12:53 PM, Wouter van der Horst <w.vanderhorst_at_gmail.com> wrote:
> > Hi,
> >
> > I am trying to set svn properties to a directory which is a junction
> > to another one, in which a checkout has been done. The error I get is:
> >
> > svn: 'D:\Projects' is not a working copy
> > svn: Can't open file 'D:\Projects\.svn\entries': The system cannot
> > find the path specified.
> >
> > The given parameter was "D:\Projects\<juncton_dir>"
> >
> > Running the same command with the 'normal' dir as parameter works fine.
> >
> > using:
> > svn, version 1.4.6 (r28521)
> > compiled Dec 20 2007, 16:19:22
> > winxp sp2
> >
> > I found this:
> > http://svn.haxx.se/tsvn/archive-2007-01/0031.shtml
> >
> > But I found nothing about this in the bugtracker. Is this a bug like
> > that post claims?
>
> Probably not: the behaviour is consistent with the Unix version when
> passing a symlink (Unix's variant of a junction) as a target.
>
>
> HTH,
>
> Erik.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-07 10:15:17 CET