Hi,
On 03/01/2022 18.16, Alec Warner wrote:
I'm trying to understand your principles here. Like on what basis do
you remove or add flags (in general).
My principals is to end-user experience over exposing as much as
possible as USE flags.
A real life example
media-sound/deadbeef
The .mp3 support can either use libmad or libmpg123. The first one is
dead upstream, while code work currently with it, because it is dead, I
rather avoid some setups where users setup +mad instead of +mpg123 that
are mutually exclusive and run into some issues, like crashes, that
would waste a lot of time on debugging it, so I made it that mp3 depends
on libmpg123 without option for libmad. Some overlay-provided ebuilds
for it do have option for libmad, I decided to not include it.
If you'd decide to give user a choice, you would make it as USE flag,
but from end-user perspective it does not provide any benefit, and from
maintainer perspective it's better to reduce error surface.
Perhaps the 'pam' example was extreme, but ipv6, or threads as Sam
shared, does not make sense to be togglable.
-- Piotr
