| 1 |
On Mon, 29 May 2017 17:33:13 +0200 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> 2.4. Backwards compatibility |
| 5 |
> ============================ |
| 6 |
|
| 7 |
|
| 8 |
Considering the discussions in that thread, a natural way to move |
| 9 |
forward now seems to be: |
| 10 |
|
| 11 |
1. Define a way to solve constraints deterministically |
| 12 |
2. Get a warning check into repoman to ensure REQUIRED_USE are solved |
| 13 |
that way. |
| 14 |
3. Get those repoman warnings fixed. |
| 15 |
4. Implement an optional FEATURES in portage for automatic solving |
| 16 |
of REQUIRED_USE. |
| 17 |
5. If all goes well, mandate that solving in next EAPI and make the |
| 18 |
repoman warning an error for those EAPIs. |
Archives