On Fri, Dec 18, 2009 at 1:36 PM, Steve Lefevre <slefevre_at_restcon.net> wrote:
>
> >
> > Looks like real_directory is the the top of your working copy, is this
> > correct?
>
> If I understand you right, that's true. It has the .svn directory.
>
> >
> > If so, what seems to be happening is that SVN (which is capable of
> > version-controlling symbolic links), is trying to commit your symbolic
> link,
>
> Oh, I see! Since a symbolic link is a filesystem file, svn thinks I'm
> tyring to commit *that symlink as a file* for a project in the current
> directory!
>
>
> > but the directory the link is in (/home/restcon) is not an SVN working
> copy
> > directory, so the commit fails right away.
> >
> > Try to run 'svn commit symlink/*', which should work just fine.
>
> That works!
>
> Should I file this as a bug report? It seems to me that svn should be smart
> enough to figure this out -- although, that would take some thinking. Svn
> is able to handle other operations intuitively, such as status.
>
>
No, this isn't a bug IMO. SVN is designed to support versioning symbolic
links. Committing changes to/under it is a scenario where it has to break
directory/link transparency because it's ambiguous what you're telling the
client to do (i.e. creating the symbolic link vs. committing the changes in
the location the new link is pointing to).
- Rob
PS - Took this off-list accidentally. Back now.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2431557
Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-12-18 19:42:14 CET