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

Re: Coping with repository bloat

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: 2004-05-14 11:38:47 CEST

Pete Gonzalez wrote:
> Our project relies on some data files and source files generated
> by various tools with lots of dependencies. It is important that
> team members are able to check out the project and compile it
> without a lot of extra setup steps and tool installations.
> In order to accomplish this, our Subversion repository has to
> store a lot of source code and binary data that changes frequently,
> and the result is that our database is accumulating a lot of dead
> wood.
> When we were using SourceSafe, this problem was solved using a
> feature called "story only latest version", which allowed the
> revision tracking to be disabled for specific files. Although
> it was a little awkward to use, it enabled us to dramatically
> reduce the database size by discarding these histories (which
> were not needed anyway).

How about a second repository which the primary repository references? You
cound keep the versions of the last two weeks there, just to be sure, and svn
automatically fetches possibly-to-be-generated files from there. It is
accomplished using the extern property(IIRC, it sure is documented).


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 14 11:39:31 2004

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.