Peter Böhm <[email protected]> writes: > I am not a Gentoo developer and have been following this thread. As a result, > I have the following question: > > Should all use flags specified by a profile be global use flags (in the sense > that > the use flag is described in the global use.desc)?
Yes, they should be, if they're in make.defaults or similar. package.* like package.use in profiles gets an exception of course. > > > In detail: > I admit that I completely misunderstood the bug at first and thought it was > about the "pipewire" use flag being activated globally. In other words, as > soon > as even one server profile is activated. Which would of course be completely > nonsensical, since not even the "alsa" use flag is activated > there. Right, of course. > After that, > I was of the opinion that all use flags that are activated by activating a > desktop profile are automatically global use flags. But that's not true. The > following use flags (besides "pipewire") are also not defined globally in > use.desc: > > - libtirpc > - pango > - qml > > All other use flags activated by a desktop profile have a global description, > even "crypt", although this use flag has very different effects (e.g., in a > Plasma profile, it installs the kde-plasma/plasma-vault package; see also: > https://wiki.gentoo.org/wiki/KDE/Troubleshooting#Can.27t_unmount_.2Fhome > ). > pkgcheck (our linting tool) actually does complain about this as it says such USE are unknown when used in the "wrong context" (a global context when not defined globally) but the problem is that it's a bit arduous to go around and make sure everything is using XYZ correctly. People do that work, e.g. I did it a year ago? 2 years ago? for Valgrind, it's just not a quick job and requires review of affected packages and possibly fixing some up. In summary: yes, you're right, though we don't always follow it. My initial reply to Roman outlines the steps needed to properly promote sometihng to a global USE flag (giving it a single definition). > [...] sam
signature.asc
Description: PGP signature
