> Not giving any opinion about out-tree-ing the .svn directories,
> I'd like to point out that it's possible to out-tree your
> workspace : for example, if you've checked out a wc/ working
> copy, you can install in wc2/ a copy of the sources you need
> (using rsync(1) for this is very efficient) or build a tree
> of symlinks (I have used this last option myself, for a project
> in which the build process was rather complicated and had a
> tendancy to mess up with the .svn directories.)
This is also another good idea, adding to the list of great
suggestions by others on the list. However, here are my issues
with it:
1) While this approach would be fine for me, it would be an extra
burden for users who may not be accustomed to manipulating files
this way.
2) Symlinks only work on filesystems which support it, leaving
rsync as the only option. Although I use Linux, many others may
be on other operating systems.
3) While disk space is inexpensive, keeping duplicate copies of
codebases that span hundreds of megabytes may still pose a
problem.
In any case, unless I run into some serious issues, I will be
posting a patch with the new feature. As I mentioned before,
I've already completed the analysis, and if I didn't miss
anything critical, it should be a pretty straightforward
and minimal change.
Thanks,
Kumaran
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 25 18:20:27 2003