| 1 |
On Donnerstag, 22. Februar 2007, Ciaran McCreesh wrote: |
| 2 |
> Inside || ( ) blocks, the package manager first removes any use? ( ) |
| 3 |
> blocks that are *immediate* (that is to say, not inside ( ) themselves) |
| 4 |
> children if the use flag is not enabled (or disabled for !use?). Then, |
| 5 |
> if the || ( ) block is empty, it is discarded. |
| 6 |
|
| 7 |
[...] |
| 8 |
|
| 9 |
> So, is there a legitimate reason for this complication to exist? Or |
| 10 |
> should use? blocks being direct children of || ( ) be forbidden? |
| 11 |
|
| 12 |
|
| 13 |
There's no other chance, than either fixing the package manager or forbidding |
| 14 |
it, I suppose. |
| 15 |
|
| 16 |
|
| 17 |
What about the use && has_version double check!? Apart from being ugly and |
| 18 |
still needed in some cases, it isn't slot safe. Why don't we let the package |
| 19 |
manager unset the use flags corresponding to stripped optional depedencies, |
| 20 |
so the use check is valid again? |
| 21 |
|
| 22 |
|
| 23 |
Carsten |
Archives