On Wed, 31 May 2017 09:54:56 +0200 Alexis Ballier <[email protected]> wrote:
> On Wed, 31 May 2017 08:51:33 +0100 > Ciaran McCreesh <[email protected]> wrote: > > > On Wed, 31 May 2017 09:35:04 +0200 > > Michał Górny <[email protected]> wrote: > > > On śro, 2017-05-31 at 08:24 +0100, Ciaran McCreesh wrote: > > > > On Wed, 31 May 2017 08:55:17 +0200 > > > > Michał Górny <[email protected]> wrote: > > > > > For example: > > > > > > > > > > foo? ( bar ) > > > > > > > > > > would mean 'if you have USE=foo, then USE=bar is enabled as > > > > > well'. > > > > > > > > What about "if bar cannot be enabled, then turn foo off"? > > > > > > Not expressible. The best you can do is 'if bar is > > > disabled, ...' > > > > This is the kind of thing that gets very messy when a user wants ssl > > enabled, and has to enable either openssl or libressl, and they're > > on a profile where openssl is masked but the ebuild writer prefers > > that option... > > > > ssl? ( ^^ ( openssl libressl ) ) with openssl masked will be reduced > to 'ssl? ( libressl )' so all good here. > Note: that's also an argument for applying user input before trying to solve anything. At the very least masks.
