Roman Žilka <[email protected]> writes: > Hi, > > in bugs.gentoo.org/970029 I'm proposing making "pipewire" a global USE > flag. It's found in multiple packages commonly present in desktop > installations (incl. qtmultimedia, gnome-shell and libsdl[23]) and > constitutes a well-defined piece of functionality.
You haven't outlined what that functionality is. > Pulseaudio, which > serves a similar purpose, already has a global flag and making > "pipewire" global as well would put it on equal footing. Moreover, the > flag's position in use.desc will put the the option to get rid of the > obnoxious daemon and its ecosystem on full display for those who see > no point in pipewire (incl. myself). It's often on by default *sigh*. I don't think this rant is appropriate (or useful) for the discussion. It does, however, inadvertently bring up an important point: PipeWire is actually more than one thing, and it is not always "just another PulseAudio". Which of these packages in their USE is actually referring to PipeWire's sound API (where it is a replacement for PulseAudio in that sense, but upstream generally say you should use the pulse API), and where is it actually screencasting (which should be USE=screencast), or something else? I'll note that I don't see many ebuilds w/ +pipewire at all, which is expected, because using the API is unusual. Going off what I know about packages but not confirmed it by looking at sources or docs: > "pipewire" is currently local in these packages in ::gentoo: > [...] > gnome-base/gnome-shell I think this may be screencasting. > gui-apps/waybar I think waybar uses it for getting information from the pipewire daemon via some additional status API. USE=pipewire indeed seems appropriate here. > gui-apps/wf-recorder This is surely screencasting given what the package does. > gui-wm/gamescope Again surely screencasting. > media-libs/libsdl2 > media-libs/libsdl3 IIRC this really does use the PipeWire sound API. > [...] So, in the end: 1) Defining a global USE flag involves giving a definition/description of that flag for use.desc. What description do you propose? 2) Are we sure that USE=pipewire does the same thing for all of these packages? That's a requirement for it being a global USE flag. If it does not currently do so, we either need to fix some of these uses, come up with a generic description s.t. it's still useful as a global USE, or abandon the global USE effort for this. 3) How many such packages are left after checking these where they may indeed be USE=screencast candidates instead? Is it above the threshold for a global USE flag? sam
signature.asc
Description: PGP signature
