On Sun, 12 Feb 2023 18:53:01 +0900 Junichi Uekawa <dan...@netfort.gr.jp> wrote:
/usr/bin/wine64-stable fails because of missing files.
Should /usr/bin/wine64-stable be there at all?
I guess having just package wine64 without package wine
installed should also work?
Then /usr/bin/wine64-stable would be needed.
Otherwise the user might really be expected to start it
via "/usr/lib/wine/wine64 wineboot", like proposed before.
At least the wrapper /usr/bin/wine from package wine
looks like it would not need "/usr/bin/wine64-stable".
Am 13.02.23 um 21:52 schrieb Jens Reyer:
On 12.02.23 10:53, Junichi Uekawa wrote:
/usr/bin/wine64-stable fails because of missing files.
Should /usr/bin/wine64-stable be there at all?
I don't know if we really need /usr/bin/wine64, or could just go with
/usr/bin/wine and the rest in /usr/lib/wine. But if we want
/usr/bin/wine64 then we also need /usr/bin/wine64-stable (for the
alternatives system).
Currently this is a link to /usr/lib/wine/wine64. Current maintainers
may replace it with a wrapper script or provide the link suggested
previously. (Or figure out why the -stable suffix in the link is now
expected by the binary, while it wasn't in the past.)
Before following commit [1] wine iterated through PATH environment
to find finally /usr/bin/wine64-stable, which is a link to ../lib/wine/wine64.
Afterwards it looks like it is "just" searching for /usr/lib/wine/wine64-stable.
Kind regards,
Bernhard
[1]
https://gitlab.winehq.org/wine/wine/-/commit/ae8562ed2277a5c051e131dc317e94aa3d5413c8
ntdll: Always use the name of the current loader to exec a new process.
[7.21]
https://gitlab.winehq.org/wine/wine/-/blob/053ee2d23d825f800baa16e455a218834aa2dec0/dlls/ntdll/unix/loader.c#L685
[7.22]
https://gitlab.winehq.org/wine/wine/-/blob/20d86f34a066657048610803e7143232efa6c0d3/dlls/ntdll/unix/loader.c#L695
