>>>>> On Sat, 08 Jul 2017, Michał Górny wrote: > On sob, 2017-07-08 at 12:26 +0200, Ulrich Mueller wrote: >> Section "Processing algorithm": >> >> > 2. Check whether the REQUIRED_USE constraint matches restrictions >> > set in #Restrictions on REQUIRED_USE format. If it does not, report >> > a REQUIRED_USE mismatch and abort. >> >> Why is this needed? This case should never occur if the REQUIRED_USE >> syntax doesn't allow it.
> The syntax is restricted from the one allowed by the PMS. The > algorithm doesn't cover the weird deep nesting cases. Unless we want > to retroactively change PMS to disallow them as well, the spec needs > to clearly establish the acceptable input for the algorithm > presented. Sorry, but that makes no sense. Why would we introduce automatic solving with the next EAPI, but at the same time not restrict REQUIRED_USE syntax to the one the solver can handle? Ulrich
pgp7n76dDaKcN.pgp
Description: PGP signature
