On Mon, 29 May 2017 17:33:13 +0200 Michał Górny <[email protected]> wrote:
> 2.4. Backwards compatibility > ============================ Considering the discussions in that thread, a natural way to move forward now seems to be: 1. Define a way to solve constraints deterministically 2. Get a warning check into repoman to ensure REQUIRED_USE are solved that way. 3. Get those repoman warnings fixed. 4. Implement an optional FEATURES in portage for automatic solving of REQUIRED_USE. 5. If all goes well, mandate that solving in next EAPI and make the repoman warning an error for those EAPIs.
