[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: a "no-.svn file" checkout?

From: Nathan Kidd <nathan-svn_at_spicycrypto.ca>
Date: 2006-03-24 22:13:58 CET

Mark_Villa@playstation.sony.com wrote:
> Subversion checkouts produce a large number of files under the '.svn'
> trees. For build-only checkouts (nothing will be checked in), the
> '.svn' trees don't serve any purpose other than to take up disk space
> and slow down copies of the checkout to other places.
>
> Is there any way to filter out '.svn' files during the checkout
> process? 'find . ...' scripts and similar time-consuming
> post-checkout processes would not be necessary if the checkout simply
> dropped these non-productive files.

'svn export' will just give you the plain files, but it means the next
time you want to get the latest files you'll have to pull them *all*
again. If you do a checkout it is much faster because it knows what
state your disk is in so you can just 'svn up' to pull only the new
changes from the repository.

IMO a good build system has properly working dependencies, so there's no
need to start with a "fresh" tree every build, meaning you can just 'svn
up' and then start your build.

Keep in mind that if you want to copy parts of your checked out build
tree somewhere, instead of using 'cp' use 'svn export' from your working
copy. It will copy the files, without the .svn directories.

-Nathan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 24 22:19:01 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.