1 |
Dear all, |
2 |
|
3 |
I'd like to suggest we introduce the following very useful feature, as soon as |
4 |
possible (which likely means in the next EAPI?): |
5 |
|
6 |
* two new files in profile directories supported, package.use.stable.mask and |
7 |
package.use.stable.force |
8 |
* syntax is identical to package.use.mask and package.use.force |
9 |
* meaning is identical to package.use.mask and package.use.force, except that |
10 |
the resulting rules are ONLY applied iff a stable keyword is in use |
11 |
|
12 |
Rationale: Often single features are "not ready for production yet", but the |
13 |
remaining package with that feature disabled would be a perfect candidate for |
14 |
stabilization. Right now this can be solved by |
15 |
* masking the useflag, which then makes the feature inaccessible even for |
16 |
~arch |
17 |
* masking the useflag for exactly one package revision, which is hell to |
18 |
maintain |
19 |
* or introducing different package revisions with/without the useflag, which |
20 |
is also a mess. |
21 |
|
22 |
Where this would (have been|be) useful: |
23 |
* we had for a long time different revisions of subversion with/without kde |
24 |
useflag |
25 |
* cups-1.4 had the infamous libusb backend triggered by USE=usb |
26 |
* cups-1.5 has optional systemd support via a systemd useflag, which pulls in |
27 |
non-stabilized systemd as dependency... |
28 |
|
29 |
Cheers, |
30 |
Andreas |
31 |
|
32 |
-- |
33 |
|
34 |
Andreas K. Huettel |
35 |
Gentoo Linux developer |
36 |
dilfridge@g.o |
37 |
http://www.akhuettel.de/ |