| 1 |
On Wed, 31 May 2017 08:51:33 +0100 |
| 2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Wed, 31 May 2017 09:35:04 +0200 |
| 5 |
> Michał Górny <mgorny@g.o> wrote: |
| 6 |
> > On śro, 2017-05-31 at 08:24 +0100, Ciaran McCreesh wrote: |
| 7 |
> > > On Wed, 31 May 2017 08:55:17 +0200 |
| 8 |
> > > Michał Górny <mgorny@g.o> wrote: |
| 9 |
> > > > For example: |
| 10 |
> > > > |
| 11 |
> > > > foo? ( bar ) |
| 12 |
> > > > |
| 13 |
> > > > would mean 'if you have USE=foo, then USE=bar is enabled as |
| 14 |
> > > > well'. |
| 15 |
> > > |
| 16 |
> > > What about "if bar cannot be enabled, then turn foo off"? |
| 17 |
> > |
| 18 |
> > Not expressible. The best you can do is 'if bar is disabled, ...' |
| 19 |
> |
| 20 |
> This is the kind of thing that gets very messy when a user wants ssl |
| 21 |
> enabled, and has to enable either openssl or libressl, and they're on |
| 22 |
> a profile where openssl is masked but the ebuild writer prefers that |
| 23 |
> option... |
| 24 |
> |
| 25 |
|
| 26 |
ssl? ( ^^ ( openssl libressl ) ) with openssl masked will be reduced to |
| 27 |
'ssl? ( libressl )' so all good here. |
Archives