1 |
On pon, 2017-04-10 at 13:52 -0400, NP-Hardass wrote: |
2 |
> On 04/10/2017 01:31 PM, Michał Górny wrote: |
3 |
> > So, the whole idea is that you can install vanilla and e.g. staging |
4 |
> > side-by-side? |
5 |
> |
6 |
> That's 50% of it. The other 50% is that since Windows applications |
7 |
> often are better supported in one version or another, you can also have |
8 |
> multiple versions installed side by side (=wine-vanilla-2.1 and |
9 |
> =wine-vanilla-2.2 for example) |
10 |
> > |
11 |
> > Is 'any' always called 'any'? Does it mean that I can have installed |
12 |
> > e.g. 'any[staging]' and 'staging', and both would be the same thing? |
13 |
> > |
14 |
> |
15 |
> Right. We were sort of at a loss for the best way to signify to the |
16 |
> user that any is for them to do whatever they want with (even if it is |
17 |
> redundant). Giving it the -any suffix was our best idea XD That said, |
18 |
> the virtual places -any in priority last, so the usually more or less |
19 |
> has to consciously decide to use it (which would for the most part avoid |
20 |
> accidental redundancy) The two primary uses of any *should* be using |
21 |
> multiple patchsets simultaneously (any[d3d9,staging]) and using any to |
22 |
> slightly alter flags from any of the others (example in the news item |
23 |
> given as using one audio system in -vanilla (gstreamer) and another in |
24 |
> -any (pulseaudio)) |
25 |
|
26 |
Honestly? I don't like that. I can see your point but I feel like it's |
27 |
pretty much having app-emulation/wine1, /wine2, /wine3... whose only |
28 |
purpose would be to allow having different USE flag sets. |
29 |
|
30 |
While of course there's really no reason to technically force all |
31 |
variants to have the same USE flags, I'm against encouraging users to |
32 |
fiddle with that more than necessary. That's an easy way to get them |
33 |
confused a lot. Just imagine that the flags set for app-emu/wine now you |
34 |
have to set for 4 packages consistently, and remember to update them or |
35 |
switching between variants is going to result in an accidental different |
36 |
build. |
37 |
|
38 |
Plus, IMHO the '-any' name is just weird. What are you going to do when |
39 |
you introduce a third patch set? Will you add four more ebuilds to cover |
40 |
all the bases? ;-) |
41 |
|
42 |
-- |
43 |
Best regards, |
44 |
Michał Górny |