Kumaran Santhanam wrote:
> Coincidentally, I started a thread just a few days ago discussing
> exactly this topic. I also feel strongly about the .svn/
> directories and believe that an SCM tool should leave the user's
> workspace pristine. Your user scenario is interesting - my
> concern has been that standard text scripting tools have to be
> told explicitly to ignore the .svn/ directories, making it harder
> to do certain types of source code analysis.
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.)
---------------------------------------------------------------------
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:10:14 2003