1 |
On czw, 2017-04-06 at 21:18 -0400, NP-Hardass wrote: |
2 |
> Plan is to move the packages into the repo as masked shortly after final |
3 |
> approval of the news item. At that point, any testers would be greatly |
4 |
> appreciated. |
5 |
> |
6 |
> The split is a little confusing for those new to the concept and there |
7 |
> have already been several internal revisions to help convey the purpose |
8 |
> of the multiple new packages. If you don't think it is clear, please |
9 |
> let me know any suggestions you might have on the wording. |
10 |
> |
11 |
> |
12 |
> |
13 |
> Title: app-emulation/wine split and slotting |
14 |
> Author: NP-Hardass <NP-Hardass@g.o> |
15 |
> Content-Type: text/plain |
16 |
> Posted: 2017-03-27 |
17 |
> Revision: 1 |
18 |
> News-Item-Format: 2.0 |
19 |
> Display-If-Installed: app-emulation/wine:0 |
20 |
> |
21 |
> Starting with Wine 2.0, Wine in Gentoo is transitioning away from its |
22 |
> traditional packaging and toward a new, split and slotted, Wine. |
23 |
> |
24 |
> As many Wine users know, there are often regressions or an application |
25 |
> works better on one version of wine than another. Going forward, |
26 |
> packaging in Gentoo will allow simultaneous installation of multiple |
27 |
> versions of Wine. |
28 |
> |
29 |
> Additionally, to expedite vanilla releases as well as permit multiple |
30 |
> configurations for each Wine installation, the major patchsets have |
31 |
> been split out into separate packages. |
32 |
> |
33 |
> Going forward, app-emulation/wine will transition to: |
34 |
> app-emulation/wine-vanilla: upstream Wine with no external patchsets |
35 |
> (like if the old packaging forced USE="-staging -d3d9") |
36 |
> app-emulation/wine-staging: Wine with Wine-Staging's patchset |
37 |
> (like if the old packaging forced USE="+staging -d3d9") |
38 |
> app-emulation/wine-d3d9: Wine with Ixit's Gallium Nine patchset |
39 |
> (like if the old packaging forced USE="-staging +d3d9") |
40 |
> app-emulation/wine-any: Wine with any of the patchsets or flags |
41 |
> (exactly like the old packaging regarding USE flags) |
42 |
> |
43 |
> wine-any exists to allow the user to build any combination that they'd |
44 |
> like (like the old packaging). This means the user could use wine-any |
45 |
> to use both Wine-Staging and Gallium Nine. Alternatively, the user |
46 |
> could use wine-any to try out another configuration from other |
47 |
> packages. For example, the user could build wine-vanilla without |
48 |
> PulseAudio, and could build wine-any with PulseAudio. The sky is the |
49 |
> limit on how a user may choose to use app-emulation/wine-any. |
50 |
> |
51 |
> Users may opt for any specific package, or may emerge virtual/wine, |
52 |
> which is provided for dependency resolution. |
53 |
> Maintainers: Please note, app-emulation/wine will be dropped, so |
54 |
> please use virtual/wine going forward. |
55 |
> |
56 |
> Users may call each version specifically, or may call a symlink based |
57 |
> on their installed patchset, for example wine-2.1, wine-staging-2.2, |
58 |
> or wine-d3d9. |
59 |
> |
60 |
> Symlinks for wine are managed with app-eselect/eselect-wine. |
61 |
> # eselect wine set wine-vanilla-2.0 |
62 |
> /usr/bin/wine -> /usr/bin/wine-vanilla-2.0 |
63 |
> # eselect wine set --staging wine-staging-2.4 |
64 |
> /usr/bin/wine-staging -> /usr/bin/wine-staging-2.4 |
65 |
|
66 |
So, the whole idea is that you can install vanilla and e.g. staging |
67 |
side-by-side? |
68 |
|
69 |
Is 'any' always called 'any'? Does it mean that I can have installed |
70 |
e.g. 'any[staging]' and 'staging', and both would be the same thing? |
71 |
|
72 |
-- |
73 |
Best regards, |
74 |
Michał Górny |