1 |
W dniu wto, 05.09.2017 o godzinie 13∶54 -0700, użytkownik Matt Turner |
2 |
napisał: |
3 |
> As an arch tester, I can tell you that it's horribly boring and |
4 |
> tedious work. I'd be happy to drop most keywords to ~arch (and Tobias |
5 |
> and I have agreed to do exactly this for alpha). In my experience as a |
6 |
> member of the MIPS team I can also tell you that fully ~arch is |
7 |
> terrible for stage building -- you're constantly dealing with generic |
8 |
> unstable problems and not with anything specific to the architecture |
9 |
> or stage building. Dropping profiles to dev/exp only exacerbate this |
10 |
> problem. |
11 |
> |
12 |
> As such, I suggest that instead we consider dropping everything |
13 |
> outside of the @system set (and its dependencies) to ~arch for select |
14 |
> architectures. This will ensure that the core system remains stable |
15 |
> and stage building goes as smoothly as possible. With the |
16 |
> significantly reduced stabilization work load, I suspect that the arch |
17 |
> testers can keep up with keyword requests and stabilization requests |
18 |
> for @system packages. |
19 |
> |
20 |
|
21 |
Talking about dropping to @system is easy. But given the horrible amount |
22 |
of USE flags involving minor dependencies, this is really hard to do. |
23 |
I think it might even be easier to actually drop to ~arch first, |
24 |
and start restoring stable keywords from there, i.e. go on as-needed |
25 |
basis rather than trying to figure out what's not needed. |
26 |
|
27 |
-- |
28 |
Best regards, |
29 |
Michał Górny |