1 |
On Sat, Jan 01, 2022 at 11:21:40PM +0100, Piotr Karbowski wrote: |
2 |
> As example I'd like to use 'ipv6' USE flag, at the moment of writing |
3 |
> this email there's 351 ebuilds in tree that expose ipv6 as USE flag, |
4 |
> allow it to be disabled. |
5 |
|
6 |
This is a flag I've usually been removing when I touch a package |
7 |
already, not that I'd want to spearhead removing it from /all/ |
8 |
packages at once but well. |
9 |
|
10 |
In most cases it's: |
11 |
- an upstream default |
12 |
- has no extra dependencies |
13 |
- doesn't increase file size in any noticeable way |
14 |
- ipv6 is expected to work |
15 |
- USE=-ipv6 tend to have less-tested code paths that I've seen cause |
16 |
issues even for ipv4 |
17 |
- not really anything to gain by disabling in a specific package even |
18 |
if you don't use ipv6, there's plenty of ways to disable ipv6 |
19 |
- majority of packages don't even have a switch to disable either way, |
20 |
this is mostly historical switches from early days of support |
21 |
|
22 |
I'd keep it if say the package needed libsuperipv6 or something as I'm |
23 |
not particularly an advocate that it /must/ be supported, and in this |
24 |
case libsuperipv6 may be less wanted or even not supported on some |
25 |
arches (maybe was written in rust!) |
26 |
|
27 |
> Beside 'ipv6', there are other USE flags that I have on mind. 'pam' |
28 |
> being another of them. |
29 |
|
30 |
That's one I think needs to be kept even if I don't like the idea of |
31 |
normal desktop system arbitrarily disabling it where about everything |
32 |
expects it to be used. |
33 |
|
34 |
Disabling can make sense on prefix, embedded systems and similar -- |
35 |
and it also need extra dependencies and cause more relevant changes |
36 |
in behavior that users should be free to want or not. |
37 |
|
38 |
Not that should be responsible for upstreams supporting disabling it, |
39 |
so when they don't just depend on it being enabled (what we do now). |
40 |
|
41 |
-- |
42 |
ionen |