Re: [gentoo-dev] bzr.eclass: The next level (this time with patch)

["René 'Necoro' Neumann" <lists@necoro.eu>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have some doubts about the usage of "co --lightweight" instead of the
plain "co". The only reason I can see is the reduced disk-space needed.
Because concerning time, the lightweight checkouts take (way) longer...

Just some bash-time tests done with the portage bzr-repo (lp:portage --
6470 revisions). I used bzr-1.12:

method		fetch	export
======		=====	======

branch: 	~47s  /	~2s
stacked branch: ~68s  /	~49s
checkout:	~46s  /	~2s
lightweight co: ~50s  /	~51s

As one can easily see: While the fetch time for co and lw-co are more or
less equal, the export time is not. As one can say, that each package is
at least exported as often as updated (if not more often), this makes
the lw co operation more or less a no-no. (Waiting one minute to get a
snapshot of a medium-sized project? ... ehm - NO)

But for completeness: size with co: 24MB - with lw-co: 3,1MB

So I'd vote for switching back to using normal checkouts (or branches -
they don't really differ in bzr for that matter).

Regards,
Necoro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkm3CeIACgkQ4UOg/zhYFuAmmQCeL/BqnCClR5CBapvAvO3Og0Tu
MBEAoINCwaNfnAYkFyxmaB2kR5BeHMsj
=37WD
-----END PGP SIGNATURE-----