Ühel kenal päeval, R, 20.07.2018 kell 01:58, kirjutas Michael Orlitzky: > On 07/20/2018 01:06 AM, Mart Raudsepp wrote: > > > > > > * They can't be undone. It's next to impossible for me to undo > > > USE=udev when set in a profile that is inherited by all > > > others. > > > > You set USE=-udev in your make.conf. > > That doesn't work, for reasons already stated. > > If I set USE="-udev" in my make.conf, I don't get the same behavior > that > I would if you left the default alone. Specifically, setting USE="- > udev" > in make.conf will disable udev support in all packages that have > IUSE="+udev", whereas now they are built WITH udev support. This > causes > severe breakage in some cases, and there's no way for me (or anyone > else) to regain the existing behavior once you turn the flag on by > default. > > > > Or in a profile that really needs this disabled. > > Yeah I'd love to except that you're proposing we add it to the > "linux" > profile, and it can't be overridden in a sub-profile for the same > reason > it can't be overridden in make.conf.
Ok, I can see that point of view for make.conf. I can't agree with changes in other profiles though, as other profile will fall under the same category in USE_ORDER (in fact, it's the same thing, as the end USE from "defaults" comes from your selected profile and it's "parent" cascade, not taken from linux profile). But maybe you have it tested and know it's a problem. Have you? For the IUSE defaults vs make.conf (and other per-system override places) problem, we should really do something about it, it keeps coming up as an issue.
signature.asc
Description: This is a digitally signed message part