Summary: | dev-db/mysql[-community] has local use flag with same name as global use flag | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marijn Schouten (RETIRED) <hkbst> |
Component: | Current packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | qa |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marijn Schouten (RETIRED)
2007-05-09 16:42:26 UTC
What exactly is wrong with specifying the use flag meaning? local and global use flags shouldn't share a single name. (In reply to comment #2) > local and global use flags shouldn't share a single name. Hmm? Can refer to any documentation about this? Not a direct requirement, but I think it follows from what is there: "If the effect of the thing USE flag upon pkg-one is substantially different from the effect it has upon pkg-two, then thing 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." http://devmanual.gentoo.org/general-concepts/use-flags/index.html By having the same name as a global use flag, the "minimal" local use flag behaves effectively as a global use flag. I don't see this as anything wrong. The global flag lists examples of what is disabled, while the local version explicitly tells you which portions are disabled (and is indeed covered under the global variant). It's not like they do different things at all. |