Re: Re: Cleaning the repository...

On 1/17/07, Sébastien Filion <sfilion@finrad.com> wrote:
> Hi,
>
> Actually, I have a project that when finishing compiling, it deletes and re-creates a new branch in which we push the new dlls.
>
> But the problem is that the delete operation on the REPO didn't erase the history in the repository for that deleted branch.

Again, this isn't a "problem" by design - it's intentional. It's a
"problem" from your perspective, but one of the many reasons to use
version control is to have a persistent, more or less immutable
history of your project.

> Maybe that this kind of files (dlls) is expensive for the Source Control??

SVN has a pretty efficient binary diffing algorithm, but when you
delete and re-create branches like you're doing, it's probably being
bypassed. If you simply updated the branch and committed the changes,
you'd see less space used.

> Anyway, if there is no best solution than the pattern DUMP\FILTER\RELOAD to clean the repository, I'll use a filesystem for that part of my project.
>
> What did you think about that?

In most projects, folks don't even store compiled files in the first
place (we ignore *.class in my Java web app, for example). The
thinking is that if you have everything required to build the DLL
stored in the repository, why are you redundantly storing the DLL?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 17 16:41:18 2007