RE: How to avoid cluttering the svn repository with several versions of compiled files
From: <webpost_at_tigris.org>
Date: Sat, 16 May 2009 08:45:05 -0700 (PDT)
Returning to Subversion-users after time away on other projects.
There's a basic flaw in Subversion: it has no graceful way to delete old files from the repository. The result is.... painful for situations like this, where the files are bulky and will clutter your source control repository. This is fundamentally a religious issue: should a source control system allow flushing old code? Subversion is clearly built with the idea of "no".
The key is to use a separate repository, accessed with 'svn:external'. Your build or commit process can commit to that separate repository, you can use subdirectories there to prevent the binary files from being stored in the same place and retaining history, and you can scrub the material from that external repository far more easily than in a location that stores both source code and binaries.
Or, switch to a source control system that handles it differently.
> Hi, I am a newbie to SVN, and have the following question:
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
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.