1 |
On 09:53 Fri 10 Jun, Alexander Berntsen wrote: |
2 |
> > So forgive me for being blind .. but we were talking about going |
3 |
> > -away- from central, curated repositories, and now we've come full |
4 |
> > circle to the situation we have now with overlays, mostly |
5 |
> > controlled in some way by gentoo .. so, do tell me .. what's the |
6 |
> > difference?! |
7 |
> Some things. For users, the main difference is that their repositories |
8 |
> are central and can be grown in a modular manner. Their repositories |
9 |
> would likely be amalgamations of our curated and reviewed |
10 |
> repositories, and some more obscure ones from specific areas they are |
11 |
> interested in. This is very similar to what we have today, save for |
12 |
> the public user repositories. A central index, as pointed out by Zac, |
13 |
> would ideally be Accompanying the public repositories. Via this hub, |
14 |
> users could review each other's ebuilds, and so on. |
15 |
|
16 |
That's great, but how are you gonna prevent nodejs-like clusterfuck |
17 |
(happened not so long ago: some guy just removed his packaged and |
18 |
suddenly everything was broken)? Or any other kind of |
19 |
screw-you-guys-im-doing-it-my-way behavior? We already have a lot of |
20 |
issues (like nobody gives a damn about broken packages for weeks) due to |
21 |
lack of manpower. In my opinion, we need more people with commit access, |
22 |
not a bunch of standalone repos managed by some random dudes. |
23 |
|
24 |
> For our central repositories, the main difference would be having more |
25 |
> repositories, to ensure that we are as modular as possible, so that |
26 |
> users can more easily e.g. pick and choose external repositories |
27 |
> instead of what we suggest and recommend, or completely get rid of |
28 |
> components they don't need or want. |
29 |
|
30 |
Splitting one giant repo in a bunch of smaller ones (like |
31 |
haskell-overlay for example) is actually a good idea. |