| 1 |
I know that portage team is closed for new features :) but this just |
| 2 |
came to my mind just 5 minutes ago and seemed good enought to try. |
| 3 |
|
| 4 |
Let's just think that portage handles 5 version of package foo and foo |
| 5 |
has "http://www.foo.org" and homepage, "GPL-v2" license and "foo just |
| 6 |
make your pc look faster" as DESCRIPTION. If we sum all the bytes that |
| 7 |
this _repeated_ info occupies in app-misc/foo we get 90 bytes (including |
| 8 |
'=' and '"' for package foo. If all the packages in portage were foo's, |
| 9 |
according to p.g.o there are 9923 packages, we would have 90*9923 witch |
| 10 |
gives us 893070bytes (893KB) of information that is repeated in many |
| 11 |
places. Also, we know that some packages have |
| 12 |
homepages/descriptions/linceses that are bigger then this so, in |
| 13 |
reality, this number will probably be bigger in real like. With portage |
| 14 |
growing every day, this will get even bigger. |
| 15 |
My ideia was to put this kind of repeated information in some other |
| 16 |
place that is not the ebuild, let's say for e.g. under app-misc/foo/info |
| 17 |
or metadata.xml. This way, users with slow connections don't download |
| 18 |
almost 1MB of info every time they sync. |
| 19 |
|
| 20 |
|
| 21 |
What do you think of this? |
Archives