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

RE: Re: how to check in a symlink?

From: Stephen Warren <swarren_at_paramanet.com>
Date: 2004-04-05 20:38:56 CEST

> From: John Peacock [mailto:jpeacock@rowman.com]
> Jeff Bowden wrote:
> > Exactly. Why would you want to check out a project with
> > symlinks on a platform that doesn't support them anyway?
> > Punting on Windows seems like the right solution.
> Why would you use a symlink in the first place?
> [HINT: it may be required to compile a sub-library]

No sub-library itself is ever going to require symlinks to compile on Windows, since Windows doesn't support links.

So, I guess you're talking about your main build scripts finding where the source etc. is for the sub-library.

In which case, I believe svn:externals will handle this very well...

Or, you "svn copy" your sub-library source into your main project", although that'll branch it. This may work if your sub-library isn't shared across multiple projects.

Or, your build system reads a config file that's checked into SVN, and the config file contains the version/path/... that indicates where the sub-library is stored. (I guess this is simulating symlinks using a text file that your build scripts know how to use)

Or, you have convention that your sub-library working copies are stored in the same directory as your main source working copy, so you know you go <main_working_copy_directory>/../<sub_library_name> to find it.

However you solve it, no Windows build script is ever going to require symlinks!

Stephen Warren, Software Engineer, Parama Networks, San Jose, CA
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 5 20:39:39 2004

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

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