| 1 |
On pon, 2017-05-29 at 20:24 +0100, Ciaran McCreesh wrote: |
| 2 |
> On Mon, 29 May 2017 17:33:13 +0200 |
| 3 |
> Michał Górny <mgorny@g.o> wrote: |
| 4 |
> > For a long time we seem to be missing appropriate tools to handle USE |
| 5 |
> > flag constraints efficiently. EAPI 4 brought REQUIRED_USE but all |
| 6 |
> > things considered, it has proven to be far from an optimal solution. |
| 7 |
> > I would therefore like to discuss adding a better tool to amend or |
| 8 |
> > replace it, to allow for automated handling of USE flag constraints. |
| 9 |
> |
| 10 |
> REQUIRED_USE's problems all come from it being thrown in at the last |
| 11 |
> minute without any testing of either the user experience or the |
| 12 |
> feasibility of its implementation. Have you implemented a prototype to |
| 13 |
> show that you can actually fix those problems? |
| 14 |
> |
| 15 |
|
| 16 |
I tend to RFC before starting the implementation. Saves effort. |
| 17 |
|
| 18 |
-- |
| 19 |
Best regards, |
| 20 |
Michał Górny |
Archives