1 |
On Sat, Jan 1, 2022 at 2:22 PM Piotr Karbowski <slashbeast@g.o> wrote: |
2 |
> |
3 |
> Hi, |
4 |
> |
5 |
> I'd like to get some insight how others see the concept of narrowing the |
6 |
> scope of USE flags in Gentoo. |
7 |
> |
8 |
> Taking a quote from devmanual: |
9 |
> |
10 |
> > USE flags are to control optional dependencies and settings which |
11 |
> the user may reasonably want to select. |
12 |
> |
13 |
> I'd like to focus on the 'reasonably want' here. While it is commonly |
14 |
> agreed on that we interface as USE flags only things that make sense to |
15 |
> be togglable, it is not always the case. It is not uncommon to see |
16 |
> packages that puts every possible option as USE flag which hardly |
17 |
> benefit anyone in some cases. |
18 |
> |
19 |
> It creates artificial choice of USE flag that makes as much sense as |
20 |
> building and trying to use solar-powered night vision googles. Possible |
21 |
> to be engineered, but makes absolute no sense to exist, yet, there will |
22 |
> be someone who will go with it and then things will not work in desired |
23 |
> way, bugs will be reported, effort will be wasted on investigation and |
24 |
> patching things up. |
25 |
> |
26 |
> As example I'd like to use 'ipv6' USE flag, at the moment of writing |
27 |
> this email there's 351 ebuilds in tree that expose ipv6 as USE flag, |
28 |
> allow it to be disabled. |
29 |
> |
30 |
> The thing is, it's 2022, and it does not make any sense to *not* support |
31 |
> IPv6, even if one does not connect to any network with IPv6, there's no |
32 |
> harm to just have it there. |
33 |
> |
34 |
> While I am all for choice, I am for choice on things that do make sense. |
35 |
> For instance, Linux kernel can be built with CONFIG_MULTIUSER=n, someone |
36 |
> could argue that since Linux kernel, that is user-configured in Gentoo, |
37 |
> can be built without support for other than UID 0, then Gentoo should |
38 |
> support it. One of the extreme examples of not supporting something that |
39 |
> does not make sense to be supported. |
40 |
> |
41 |
> Beside 'ipv6', there are other USE flags that I have on mind. 'pam' |
42 |
> being another of them. |
43 |
> |
44 |
> Whats your view on it? |
45 |
|
46 |
I'm trying to understand your principles here. Like on what basis do |
47 |
you remove or add flags (in general). |
48 |
|
49 |
I want to remove: |
50 |
- bash-completion |
51 |
- acl |
52 |
- ldap |
53 |
- policykit |
54 |
- readline |
55 |
- sound |
56 |
|
57 |
(Part of this is just to have a meta discussion so we settle on some |
58 |
driving principles on why we keep one flag over the other.) |
59 |
|
60 |
I can easily craft a narrative for getting rid of ipv6, for example, |
61 |
but I cannot really craft a good narrative for getting rid of pam, or |
62 |
policykit, or ldap as flags. So why do we keep some and remove others? |
63 |
|
64 |
-A |
65 |
|
66 |
> |
67 |
> -- Piotr. |
68 |
> |