Quoting Nick Jennings <nick_at_cmdwebsites.com>:
> I have a local checkout of a project I'm working on, the code
> makes heavy use of symlinks using absolute paths (such as linking to
> /<project>/<foo>/<bar>/<file>). On the system /<project> is a symlink
> to the master (live) checkout of the project. Basically there is a lot
> of linking within the project and in order to be clear about where
> things link to, the designer decided to use these absolute paths.
>
> So, I'm developing on the same system, but obviously I want all the
> symlinks to point to /<mycheckout>/* . I made a quick shell script to
> re-link the files in my checkout and everything works great.
>
> However: when I do an 'svn status' all the symlinks show up as M and of
> course I never want to commit these files, (though I might want to
> commit the files they link to). Is there any way to in effect ignore
> all these symlinks? So when I do an 'svn status' I only see the files
> that I've modified during my development?
>
> I know it's kind of a strange request, but I'm trying to avoid setting
> up an entire chroot system just for some quick development work.
I see this as another case of this situation:
http://subversion.tigris.org/faq.html#ignore-commit
The answer is: do not put those symlinks into the repository. Instead,
you could create a script which is in the repository, and the script
creates the symlinks on the developer system to point to the right
place. And add svn:ignore properties to the directories to ignore the
unversioned symlinks.
Or, use relative symlinks so that they always work, regardless of
where the working copy is.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-03 20:00:49 CEST