launchpad-dev team mailing list archive

[Gary Poster <gary.poster@xxxxxxxxxxxxx>]

On Mar 10, 2011, at 9:29 AM, Aaron Bentley wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 11-03-09 04:51 PM, Robert Collins wrote:
>>> Is there any reason why we should not clean this up and remove old versions?
>> 
>> No reason. Long as we have all versions covered by:
>> - last db deploy
>> - db devel
>> - devel
> 
> A Bazaar branch seems like a poor way to manage the sourcedeps, because
> each new version takes up the same amount of space, and that space is
> taken up permanently in the history (modulo ghosts).
> 
> If we want to maintain a full history of every version, we could ungzip
> the tarfiles and maintain file-ids as we replace versions.  That would
> allow Bazaar's delta compression to work.  It would also mean that every
> launchpad branch would be associated with a particular revision of the
> sourcedeps branch.
> 
> But I don't know if having a fully versioned history is actually needed.
> If it's not, couldn't we just have a directory on devpad that we rsync,
> which has all the latest versions required by last db deploy, db stable,
> and stable (okay, db devel and devel too)?

If we are actually looking for a better approach that requires some work, there are a few standard patterns that are usually followed for zc.buildout.  We don't need to innovate if we want to put some time into it.  That said, this is far from a priority problem AFAIK.

Gary