| 1 |
On Sat, 01 Sep 2012 11:15:16 -0700 |
| 2 |
Zac Medico <zmedico@g.o> wrote: |
| 3 |
> This sounds more like a user-interface issue than a problem with |
| 4 |
> runtime-switchable USE flags (GLEP 62). The nice thing about |
| 5 |
> runtime-switchable USE flags is that makes it possible to allow users |
| 6 |
> to unify all of their optional dependency choices in their USE flag |
| 7 |
> settings. |
| 8 |
|
| 9 |
The nice thing about GLEP 62 is that no-one has implemented it and tried |
| 10 |
it with lots of packages and a bunch of users, thus figuring out just |
| 11 |
how much of a pain in the ass getting this right is... Right now we're |
| 12 |
debating the merits of a tried and tested solution versus an entirely |
| 13 |
hypothetical idea. |
| 14 |
|
| 15 |
If you really think unification is an advantage, you could treat |
| 16 |
exheres-style suggestion names as a special USE_EXPAND group. But |
| 17 |
practical experience suggests that suggestions *shouldn't* be unified, |
| 18 |
and that the way to make the feature useful to users is to get the user |
| 19 |
to explicitly accept or reject suggestions, and to make suggestions look |
| 20 |
like suggestions. |
| 21 |
|
| 22 |
-- |
| 23 |
Ciaran McCreesh |
Archives