| 1 |
On 04/10/2017 01:31 PM, Michał Górny wrote: |
| 2 |
> So, the whole idea is that you can install vanilla and e.g. staging |
| 3 |
> side-by-side? |
| 4 |
|
| 5 |
That's 50% of it. The other 50% is that since Windows applications |
| 6 |
often are better supported in one version or another, you can also have |
| 7 |
multiple versions installed side by side (=wine-vanilla-2.1 and |
| 8 |
=wine-vanilla-2.2 for example) |
| 9 |
> |
| 10 |
> Is 'any' always called 'any'? Does it mean that I can have installed |
| 11 |
> e.g. 'any[staging]' and 'staging', and both would be the same thing? |
| 12 |
> |
| 13 |
Right. We were sort of at a loss for the best way to signify to the |
| 14 |
user that any is for them to do whatever they want with (even if it is |
| 15 |
redundant). Giving it the -any suffix was our best idea XD That said, |
| 16 |
the virtual places -any in priority last, so the usually more or less |
| 17 |
has to consciously decide to use it (which would for the most part avoid |
| 18 |
accidental redundancy) The two primary uses of any *should* be using |
| 19 |
multiple patchsets simultaneously (any[d3d9,staging]) and using any to |
| 20 |
slightly alter flags from any of the others (example in the news item |
| 21 |
given as using one audio system in -vanilla (gstreamer) and another in |
| 22 |
-any (pulseaudio)) |
| 23 |
|
| 24 |
-- |
| 25 |
NP-Hardass |
Archives