Open milahu opened 3 months ago
Having this kind of fallback is certainly a good idea. Added to my todo - though PR welcome ;)
two seconds ^^
ideally i want to setup the wine env only once in the read-only package store
so im running wenv init
as part of the build process
just the default wineprefix is wrong, its based on the python interpreter location...
related issue:
this will not work with unpatched wine
if (st.st_uid != getuid()) fatal_error( "%s is not owned by you\n", config_dir );
wine complains about the ownership of WINEPREFIX
$ ./result/bin/wenv python
wine: '/nix/store/mcbrxyi2q7kksyrxm7px9l0ik3rxv94h-wenv-0.5.1/share/wenv/win32' is not owned by you
WINEPREFIX is not owned by you
i found many discussions on this problem but no solution to make wine ignore the ownership workarounds: sudo, chown, symlinks, bind mount, LD_PRELOAD, ...
but this issue remains:
if the default WENV_PREFIX
is read-only
then wenv should fallback to $HOME/.cache/wenv
ideally the "cache" config should be a list of paths for reading from the cache, all cache paths are used for writing to the cache, the first writable cache path is used
by default, wenv fails with a read-only prefix
wenv/_core/env.py
wenv/_core/config.py
workaround: set env
WENV_WINEPREFIX=/some/where/else
orWENV_PREFIX=/some/where/else
expected: if the default wineprefix is read-only then fallback to
$HOME/.cache/wenv/wine
via platformdirssimilar #14