Summary: | Several global USE flags should be local | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sixpointzero |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
sixpointzero
2016-10-03 19:44:42 UTC
As per the Devmanual [1] > Local and Global USE Flags > USE flags are categorised as either local or global. A global USE flag must satisfy several criteria: > > It is used by many different packages, at least 5 seems to be agreed upon. > It has a general non-specific purpose. > The second point is important. If the effect of the USE flag upon pkg-one is substantially different from the effect it has upon pkg-two, then the flag is not a suitable candidate for being made a global flag. In particular, note that if client and server USE flags are ever introduced, they can not be global USE flags for this reason. > > Before introducing a new global USE flag, it must be discussed on the gentoo-dev mailing list. These flags were introduced after this discussion [2]. As per the guidelines set forth in the devmanual, global USE flags are discussed on the developer mailing list, so I'd recommend posting there asking for any opinions on reconsidering them as local instead of global. [1] https://devmanual.gentoo.org/general-concepts/use-flags/index.html [2] https://archives.gentoo.org/gentoo-dev/message/e14b29676661c9d3e6e95c2930a73b60 Please send inquiries like these to the -dev mailing list. |