On Mon, 29 May 2017 21:42:33 +0200 Michał Górny <mgo...@gentoo.org> wrote: > On pon, 2017-05-29 at 20:24 +0100, Ciaran McCreesh wrote: > > On Mon, 29 May 2017 17:33:13 +0200 > > Michał Górny <mgo...@gentoo.org> wrote: > > > For a long time we seem to be missing appropriate tools to handle > > > USE flag constraints efficiently. EAPI 4 brought REQUIRED_USE but > > > all things considered, it has proven to be far from an optimal > > > solution. I would therefore like to discuss adding a better tool > > > to amend or replace it, to allow for automated handling of USE > > > flag constraints. > > > > REQUIRED_USE's problems all come from it being thrown in at the last > > minute without any testing of either the user experience or the > > feasibility of its implementation. Have you implemented a prototype > > to show that you can actually fix those problems? > > I tend to RFC before starting the implementation. Saves effort.
Not the implementation. A prototype implementation. As we saw from REQUIRED_USE, it really doesn't save effort to spend time specifying something that can't even remotely work... -- Ciaran McCreesh
