diff options
| author |   Michał Górny <mgorny@gentoo.org> | 2017-07-09 08:05:26 +0000 |
|---|---|---|
| committer | Michał Górny <mgorny@gentoo.org> | 2017-07-09 08:05:26 +0000 |
| commit | b6d3b78af2316d853afcf5115496054bc89b2d11 (patch) | |
| tree | 49977ac6e52520336861e458b7c087b48bdd3d3c | |
| parent | /* Restrictions for allowed REQUIRED_USE syntax */ ban on empty groups (diff) | |
| download | glep-b6d3b78af2316d853afcf5115496054bc89b2d11.tar.gz glep-b6d3b78af2316d853afcf5115496054bc89b2d11.tar.bz2 glep-b6d3b78af2316d853afcf5115496054bc89b2d11.zip | |
/* Empty any-of, at-most-one-of, exactly-one-of groups */ use counts
| -rw-r--r-- | GLEP:73.mw | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -363,6 +363,8 @@ It is unclear whether this is the most correct behavior logically though. Alexis Since the original use case does not apply here (USE-conditional groups are banned inside those operators), the correct behavior is unclear and this has no real use case, banning it seems like the best course of action. +There is not a single use of such groups at the time of writing, and their natural occurrence is extremely unlikely. It has some potential of occurring due to eclass-generated strings but it is doubtful whether any of such cases would not be more appropriately reported as an error. + ===Solving algorithm=== The solving algorithm attempts to enforce REQUIRED_USE in the most natural way, interpreting the constraints as developer suggestions on how to make the constraint apply. |