On Sat, May 16, 2020 at 5:03 PM Esme Povirk (they/them) < vincent(a)codeweavers.com> wrote:
Doesn't it defeat the purpose of using symlinks that resolve properly if they only work inside wine processes?
The way this is put together you can run "wineprefix <program> <arguments>" to allow these symlinks to resolve properly. The default behavior (no arguments) is to open bash, and this behavior propagates such that applications run within the shell work the same way, a couple examples: === ehoover(a)lappy:~$ wineprefix ehoover(a)lappy:/??/C:$ echo "TEST" | gpg -c --batch --yes --passphrase "test" --output /??/C:/TEST/test.gpg - ehoover(a)lappy:/??/C:$ exit ehoover(a)lappy:~$ wineprefix gpg -d /??/C:/TEST/test.gpg gpg: AES256 encrypted data gpg: encrypted with 1 passphrase TEST === So, the symlinks do work for non-wine processors (when launched with the special LD_PRELOAD). Also, this is only necessary for within-prefix links - any symlinks targeting outside the prefix would not require any special treatment. Best, Erich