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

RE: SVN Overwrite & .SVN size

From: Ulrich Eckhardt <Eckhardt_at_satorlaser.com>
Date: 2005-11-03 12:52:13 CET

Mr keerti nayak wrote:
> 1. The whole source tree is about 2 GB in size. But unfortunatly
> after migrating to SVN when I tried to checkout the code, its around
> 8 GB in size. Thats mainly due to addition of .svn directories. Can I
> avoid this?

There were quite a few requests to structure working copies differently in order to reduce or avoid this overhead, but currently there is no solution but to only selectively check out the parts of your sourcecode you're working on.

> 2. SVN doesnt provide over-write option when we need to checkout. In
> the current scenario I have some 10% source's checked in and the rest
> are provided by a third party. The code that is checked is used to
> customize the third party software. Hence only the files that is
> customized is checked in the SCM system. It doesnt make sense to
> version control the third party software. When I checkout I need to
> only over-write the customized code i.e. checkout on an existing
> folder. How is it possible through Subversion?

I'm not exactly sure I understand what you're trying to do. However, I personally find it a good idea to also version 3rd party libraries, if just to be able to recover older versions, to have one place where things can be found and to be able to version-control local adaptions. There is a script called svn_load_dirs which is designed to help with this. Using Subversions merging capabilities, this helps immensely managing local and upstream changing libraries. BTW, I also use this for binary only libraries, the only difference that there are no local changes.

Typically, it goes like this:
1. use svn_load_dirs to load version 42 into the repository
2. make a branch 42-mod where to apply local changes
3. weeks pass
4. use svn_load_dirs to load version 43 into the repository
5. make a branch 43-mod
6. merge the the changes from branch 42-mod into branch 43-mod
7. flush, rinse and repeat


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 3 12:54:19 2005

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.