1 |
Carlos Silva wrote: |
2 |
> I know that portage team is closed for new features :) but this just |
3 |
> came to my mind just 5 minutes ago and seemed good enought to try. |
4 |
> |
5 |
> Let's just think that portage handles 5 version of package foo and foo |
6 |
> has "http://www.foo.org" and homepage, "GPL-v2" license and "foo just |
7 |
> make your pc look faster" as DESCRIPTION. If we sum all the bytes that |
8 |
> this _repeated_ info occupies in app-misc/foo we get 90 bytes (including |
9 |
> '=' and '"' for package foo. If all the packages in portage were foo's, |
10 |
> according to p.g.o there are 9923 packages, we would have 90*9923 witch |
11 |
> gives us 893070bytes (893KB) of information that is repeated in many |
12 |
> places. Also, we know that some packages have |
13 |
> homepages/descriptions/linceses that are bigger then this so, in |
14 |
> reality, this number will probably be bigger in real like. With portage |
15 |
> growing every day, this will get even bigger. |
16 |
> My ideia was to put this kind of repeated information in some other |
17 |
> place that is not the ebuild, let's say for e.g. under app-misc/foo/info |
18 |
> or metadata.xml. This way, users with slow connections don't download |
19 |
> almost 1MB of info every time they sync. |
20 |
> |
21 |
> |
22 |
> What do you think of this? |
23 |
|
24 |
Not going to happen anytime soon. Would introduce xml parsing code in |
25 |
core portage functions (bad), removing the info from ebuilds breaks |
26 |
compability (very bad) and there isn't any real benefit. You're not |
27 |
going to save any significant amount (= more than a *few* KB) of space |
28 |
during transmission or on disc. |
29 |
|
30 |
Marius |
31 |
-- |
32 |
gentoo-dev@g.o mailing list |