>>>>> On Tue, 7 Feb 2017, Ian Stakenvicius wrote: > On 07/02/17 08:27 AM, Michael Orlitzky wrote: >> >> The thread wasn't about discouraging IUSE defaults, rather to >> decide when they are appropriate. You cannot omit "pkginternal" >> from USE_ORDER, because you will break all of the packages whose >> defaults are either critical to the package, or prevent a >> REQUIRED_USE conflict.
"The package manager may use it as a suggestion" seems pretty clear. PMS doesn't require that a package manager honours these defaults. So if anything is broken after removing them from USE_ORDER, then it was already broken before. Conversely, I don't see why package maintainers shouldn't use IUSE defaults to enable (or disable, though that is rarely used) those flags that they deem the package's best default configuration. > OK, can we all decide out of this thread, that if any package is > enabling critical functionality via IUSE-defaults (or rather, IUSE > defaults alone), that this be addressed through package.use.force in > profiles OR through removal of the flag? Right. Also REQUIRED_USE should be used sparingly, and only for libraries whose reverse USE dependencies would otherwise break. In all other cases, fall back to a reasonable default if flag settings are incompatible. Ulrich
pgpUTmETBG0Pn.pgp
Description: PGP signature
