1 |
On 09/01/2012 09:00 AM, Ciaran McCreesh wrote: |
2 |
> On Fri, 31 Aug 2012 18:45:59 -0700 |
3 |
> Zac Medico <zmedico@g.o> wrote: |
4 |
>> On 08/31/2012 04:07 PM, Ciaran McCreesh wrote: |
5 |
>>> On Fri, 31 Aug 2012 16:03:25 -0700 |
6 |
>>> Zac Medico <zmedico@g.o> wrote: |
7 |
>>>>> runtime-switchable USE flags for optional dependencies o.O? It |
8 |
>>>>> sounds like using a spoon to eat spaghetti to me. |
9 |
>>>> |
10 |
>>>> All suggested deps are not equal, so USE flags give you the |
11 |
>>>> ability to pick and choose the ones that you want. |
12 |
>>> |
13 |
>>> So does --take / --ignore with suggested dependencies, with the |
14 |
>>> added advantage that suggested packages don't end up being brought |
15 |
>>> in without user request just because a user has a particular use |
16 |
>>> flag enabled globally. |
17 |
>> |
18 |
>> If the USE flags have ambiguous meanings doesn't that mean that |
19 |
>> they've been poorly named? |
20 |
> |
21 |
> It's not like that. It's that in practice, suggestions are mostly for a |
22 |
> particular specific feature (such as git-send-email support), not for a |
23 |
> general concept (such as email in general). |
24 |
> |
25 |
> It also defeats the point of suggestions, if they're not made visible. |
26 |
> For users, suggestions should look like suggestions, and they should |
27 |
> be able to see them easily. |
28 |
|
29 |
This sounds more like a user-interface issue than a problem with |
30 |
runtime-switchable USE flags (GLEP 62). The nice thing about |
31 |
runtime-switchable USE flags is that makes it possible to allow users to |
32 |
unify all of their optional dependency choices in their USE flag settings. |
33 |
|
34 |
You can still implement a --take / --ignore mechanism while allowing the |
35 |
use of runtime-switchable USE conditionals in SDEPEND. It's simply a |
36 |
matter of ignoring the USE conditionals and instead using your --take / |
37 |
--ignore mechanism to select atoms. |
38 |
-- |
39 |
Thanks, |
40 |
Zac |