Mark Richards wrote:
> Looks like there may be something available in the Windows filesystem to
> maintain symbolic links. That would be nice if one wanted to run a
> repository on the windows filesystem and store unix files in it.
?!? Of course you can store symlinks in a windows repository. Subversion
provides (or actually *is*) a versioned file system that is designed to
handle Unix files. This versioned file system (repository) is only *stored*
in BDB or fsfs files on the servers file system. The repository is a
container for your versioned file system as a word DOC document is a
container for your markup enriched texts. You wouldn't expect to be able
to make your *files* bold or italic, do you?
As far as I understand your problem is not on the repository side. Your
problem is that your working copies rely on features of common unix file
systems. A working copy is a copy of a certain revision (or a mix of
certain revisions) of your repository in your local file system. Since
your're checking out in windows, your local file system is accessed by
TSVN using Windows APIs. Windows APIs have no idea what symlinks are, there
is currently no way of creating symlinks with Windows APIs. So it's
impossible to check out symlinks into your Windows working copy that
behave like symlinks in your working copy.
I'm working in a Unix/Windows environment and tried both clients and
svnserve under Unix and Windows. Judging from this experiences I can
offer three advices to you:
1. If you have a Unix box available, make it your Subversion server.
svnserve is hell lot faster on Unix, than on Windows. For repositories
that are used over the network it's ususally better to use the svn: or
http: protocol rather than to access the repository directly via file:.
2. Use TSVN for you Windows working copies
3. Use the native CLI or a native/JAVA GUI client for your Unix working
copies. You won't find a GUI client that's as mighty, well-reasoned and
stable as TSVN but you will find one that satisfies your needs. If not,
use scripts or write a wrapper to manipulate your working copies. You can
still use TSVN for browsing, diffing etc.
You also might want to consider your using of symlinks. Maybe you can
substitute your symlinks by svn:externals. Or you might want to
accept some redundancies (and their disadvantages) for the pleasure
to use TSVN (as I did).
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Aug 10 01:56:53 2005