1 |
Hi, |
2 |
|
3 |
When the size of the repo is considered too big maybe we can revisit the option |
4 |
of having the portage tree distributed as a compressed sqashfs image. |
5 |
|
6 |
$ du -hs /var/db/repos/gentoo |
7 |
536M . |
8 |
$ gensquashfs -k -q -b 1M -D /var/db/repos/gentoo -c zstd -X level=22 /tmp/gentoo-current.zstd.sqfs |
9 |
$ du -h /tmp/gentoo-current.zstd.sqfs |
10 |
47M /tmp/gentoo-current.zstd.sqfs |
11 |
|
12 |
Though that would probably open another can of worms around incremental updates |
13 |
to the portage tree, or more precisely the lack of it (i.e. increased bandwidth |
14 |
requirements). |
15 |
|
16 |
Regardless, as a proxied maintainer I agree with Flow's point of view here (I |
17 |
think I have expressed these in detail too in the past here) and would prefer |
18 |
undeprecating EGO_SUM. |
19 |
|
20 |
Zoltan |
21 |
|
22 |
On Fri, Sep 30, 2022 at 05:10:10PM +0200, Jaco Kroon wrote: |
23 |
> Hi, |
24 |
> |
25 |
> On 2022/09/30 16:53, Florian Schmaus wrote: |
26 |
> > jkroon@plastiekpoot ~ $ du -sh /var/db/repos/gentoo/ |
27 |
> >> 644M /var/db/repos/gentoo/ |
28 |
> >> |
29 |
> >> I'm not against exploding this by another 200 or even 300 MB personally, |
30 |
> >> but I do agree that pointless bloat is bad, and ideally we want to |
31 |
> >> shrink the size requirements of the portage tree rather than enlarge. |
32 |
> > |
33 |
> > What is the problem if it is 400 MB more? ? What if we double the |
34 |
> > size? Would something break for you? Does that mean we should not add |
35 |
> > more packages to ::gentoo? Where do you draw the line? Would you |
36 |
> > rather have interested persons contribute to Gentoo or drive them away |
37 |
> > due the struggle that the EGO_SUM deprecation causes? |
38 |
> How long is a piece of string? |
39 |
> |
40 |
> I agree with you entirely. But if the tree gets to 10GB? |
41 |
> |
42 |
> At some point it may be worthwhile to split the tree similar to what |
43 |
> Debian does (or did, haven't checked in a while) where there is a core, |
44 |
> non-core repo etc ... except I suspect it may be better to split into |
45 |
> classes of packages, eg, x11 (aka desktop) style packages etc, and keep |
46 |
> ::gentoo primarily to system stuff (which is also getting harder and |
47 |
> harder to define). And this also makes it harder for maintainers. And |
48 |
> this is really already what separate overlays does except the don't (as |
49 |
> far as I know) have the rigorous QA that ::gentoo has. |
50 |
> |
51 |
> But again - at what point do you do this - and this also adds extra |
52 |
> burden on maintainers and developers alike. |
53 |
> |
54 |
> And of course I could set a filter to not even --sync say /x11-* at |
55 |
> all. For example. Or /dev-go or /dev-php etc ... |
56 |
> |
57 |
> So perhaps you're right, this is a moot discussion. Perhaps we should |
58 |
> just say let's solve the problem when (if?) people complain the tree is |
59 |
> too big. No, I'm not being sarcastic, just blunt (; |
60 |
> |
61 |
> The majority of Gentoo users (in my experience) are probably of the |
62 |
> developer oriented mindset either way, or have very specific itches that |
63 |
> need scratching that's hard to scratch with other distributions. Let's |
64 |
> face it, Gentoo to begin with should probably not be considered an |
65 |
> "easy" distribution. But it is a highly flexible, pro-choice, extremely |
66 |
> customizable, rolling release distribution. Which scratches my itch. |
67 |
> |
68 |
> Incidentally, the only categories currently to individually exceed 10MB |
69 |
> are these: |
70 |
> |
71 |
> 11M media-libs |
72 |
> 11M net-misc |
73 |
> 12M dev-util |
74 |
> 13M dev-ruby |
75 |
> 16M dev-libs |
76 |
> 30M dev-perl |
77 |
> 31M dev-python |
78 |
> |
79 |
> And by far the biggest consumer of space: |
80 |
> |
81 |
> 124M metadata |
82 |
> |
83 |
> Kind Regards, |
84 |
> Jaco |
85 |
> |