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

Re: History in subversion

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Mon, 17 Jun 2013 17:13:46 -0500

On Mon, Jun 17, 2013 at 4:09 PM, Olivier Antoine
<oliviera201304_at_gmail.com> wrote:
>> The common scenario is to have multiple 'projects' under the same
>> repository root, each with their own trunk/branches/tags tree.
> To be honest, I'm afraid of several projects sharing a same revision
> numbering.
> Repository gets bigger and bigger, problems with disk space arise, one
> project wants to leave the repo,
> but there is not enough space even to run svn+dump, finally a new repo is
> created for the project (and the project asks to remove empty revisions ...
> !).
> I would prefer to create one repo per project, with one triplet of
> directories trunk+branches+tags.

That's a reasonable choice - and with a repo approaching 80GB I
understand the issue although it has not been an actual problem yet.
However, other than the sheer size of the dump/filter operation,
extracting a portion should be practical even if you renumber as long
as you have made tags and use those human-friendly tag names for
externals and other specific revisions you need to reference
consistently instead of peg revision numbers.

>> You can use hook scripts for that.
>> We sometimes check out source from tags and commit the resulting binaries
>> back
>> - not exactly 'clean' but pragmatically useful - and possible with an
>> appropriate script
>> that allows this exception.
> Hum ... are these scripts "downloadable" somewhere, or do we have to write
> them ... ?

Various versions have been posted to forums - and are fairly easy to
find with a google search. I'm not sure if there is an 'official'
collection anywhere.

   Les Mikesell
Received on 2013-06-18 00:14:20 CEST

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.