I was reading through the subversion FAQ to see if there was support for
symlinks, and read that there was not, and why. You asked for proposals
thereafter, and I have one for you.
Now, I may not have read up on things well enough, and the two following
structures might exist - but as far as I know, they do not.
As for directly addressing the issue for symlinks, I feel that the best
you could do is to make an svn:custom or svn:special or whatnot, sort of
tag for users to make standard files that equate to symlink instructions
and then. Users could then make standard files containing symlink
instructions, and tag them with this tag and a certain value. You could
make an easy to use script or whatnot to read the values back from this
tag, and the users could utilize this script with one of their own to
extract the data from those files and regenerate them into the proper
sorts of links, or anything they wanted really, for their system.
A nice, related feature, would be an svn:mirror tag. A standard file
would be created, then tagged with this tag, with the
value of the tag being a relative path to another section of the
repository. Upon next check out, the SVN server would see this tag and
automatically replace that file with the structure being mirrored,
retaining the tag, and also gaining an svn:mirrored tag for that file,
and anything in a mirrored directory and its subdirectories if that is
the case. If a user checks in an svn:mirrored file, the user is warned
that it is a mirrored copy and should be manually merged with what it is
mirroring if the user wants the changes to take effect, otherwise the
changes will be dropped and on the next check out replaced with the
contents of the file/dir the svn:mirror tag points to.
I am relatively new to the svn/cvs concept, but I am not sure how one
would keep two sections of a repository completely in sync for each
check in and check out without doing it manually, this mirror tag would
allow for that.
By the way, SVN is FANTASTIC, I am implimenting it for our college's
computer science department, and have written a rather shabby, but
functional front end for the administrative poriton of it in perl so other
students can access it securely and easily on the web. Keep up the great
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jul 22 20:13:34 2004