1 |
Ciaran McCreesh schrieb: |
2 |
>> * two new files in profile directories supported, |
3 |
>> package.use.stable.mask and package.use.stable.force |
4 |
>> * syntax is identical to package.use.mask and package.use.force |
5 |
>> * meaning is identical to package.use.mask and package.use.force, |
6 |
>> except that the resulting rules are ONLY applied iff a stable keyword |
7 |
>> is in use |
8 |
> This means that an ebuild will effectively change when moved from ~arch |
9 |
> to arch. The point of ~arch is to test ebuilds before they're moved to |
10 |
> arch. |
11 |
|
12 |
I agree that the ~arch ebuilds should be tested in the same |
13 |
configuration in which they will end up in arch. However in this case, |
14 |
the possible configurations for arch are a subset of those in ~arch, so |
15 |
the testing covers those too. |
16 |
|
17 |
I see a problem where a significant proportion of ~arch users will have |
18 |
this flag enabled (which is obviously the point of |
19 |
package.use.stable.mask) so the arch configurations will see fewer |
20 |
testers. This issue may need to be addressed, e.g. by extending |
21 |
stabilization period or disallowing package.use.stable.mask in default |
22 |
or desktop profile. |
23 |
|
24 |
|
25 |
Best regards, |
26 |
Chí-Thanh Christopher Nguyễn |