> Since Windows doesn't support symlinks, the only way to
> handle it is to make a
> copy (possibly readonly), when trying to port that
> application to Windows. While
> it is true that no Windows-target application will ever use
> symlinks, the entire
> world is not running Windows.
For my $0.02 worth, I don't need symbolic links, but what I do need is
svn:externals to support files. If my reading of the documentation is
correct, svn:externals only supports directories, which is a little too
broad for me.
For a little bit of help, here is how I want to use symbolic links /
svn:externals: I want to have a project directory, with a 'lib'
subdirectory. Parallel to that, I ant to have a 3ps (third party
software) directory containing all the source code, documentation, and
deliverable libraries for the third party software I'm using. Something
like this:
- project
+ source
+ lib
+ common.jar ->
/3ps/common-collection/2.1/docs/lib/common-collection.jar
-3ps
+ common-collection
+ 2.1
+ docs
+ lib
+ common-collection.jar
I want my project's lib directory to be composed of links (symbolic or
external) directing to the libraries necessary to compile / run my
application. Now, my build script simply needs to add all the *.jar
files to my compiler's classpath and compile. Additionally, the version
numbers of all my dependencies would be version controlled by the links.
Hopefully this is enough to describe what I would like to see.
So, basically, I would like to see a compromise of sorts: svn:externals
applicable to files. This prevents the problem of duplicate
modification problem of copying (where both source and target have been
modified) on windows system, as SVN wouldn't accept any modifications to
the target of the 'link'.
Again, just my pitiful $0.02.
JDG
--
Jay Glanville
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 5 21:55:36 2004