Patrick Johnson wrote:
> I found that this issue crops up in a few other places as well, such
> as IDEs that want to parse the source directory tree and get
> confused or bogged down by the .svn directories.
Personally I like the .svn (and RCS, CVS, {arch}, .git) directories to
be in the working copy. This makes the working copy transportable. I
have worked with other systems that put those in the home directory
and personally have had problems with them. I really dislike a shared
config file or a shared repository in my home directory. I really
like the distributed .svn directories much better.
> I'm not ready to make the move to svk, so I wrote a little Perl
> script, "adirstasher" to temporarily move the administrative .svn
> directories out of the way, then move them back.
>
> http://svn.haxx.se/users/archive-2006-05/0739.shtml
>
> It seems risky, but I have used it a couple of times without disaster.
Thanks for sharing your perl script. Regardless of philosophical
differences I wanted to say thanks. But if GoLive is having this
problem I would have thought it would be better to svn export the
directory instead. Or I would use rsync to copy from a staging
location into the live location to create a mirror without the .svn
files.
rsync -n -a --delete --exclude .svn --delete-excluded /from/here /to/there
Thanks
Bob
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 22 22:14:34 2006