On Thu, Jan 20, 2005 at 10:25:55PM -0600, Daniel Goller wrote: > Note: The implementation ideas are just that. Ideas. If you find some > structural flaw in them, tell us, don't flame :-) I have a identified a problem that this will cause... Ok, so we're keeping all old versions of the eclasses to satisfy your proposed plan. This will have a major negative impact on the size of the tree.
Let's focus on a specific example: eutils.eclass, the mainstay of a lot of development. It's currently revision 1.141. Current file size is 42243 bytes. Average file size over those 141 revisions is 28308 bytes. If we had to keep ALL of these 141 revisions, that bloats the tree by 3991553 bytes. This file is not typical of eclasses, as it's a good deal larger than many others, and has the most revisions, but it ideal for pointing out what the end result could be. I make a rough total for keeping every revision of every ebuild as 15+ MB of data. (Assuming 4kb blocks for files smaller than 4kb). This is nearly an 18% increase in the size of the tree. We're already trying to get it down (expect my email later today about stuff in files/ violating the 20k goal). -- Robin Hugh Johnson E-Mail : [EMAIL PROTECTED] Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
pgpz8beHvZdZE.pgp
Description: PGP signature
