Re: [PATCH v7 0/2] MR3259: Add environment variable to isolate WINEPREFIX at creation

[Fabian Maurer (＠DarkShadow44)]

On Mon Nov 13 21:02:03 2023 +0000, Alexandre Julliard wrote:
> > Well, I target the parts where the folders are created, where else
> > could I handle it? I currently don't see a better way to do this. Mind
> > pointing me into the direction of a better design?
> > I don't mean the code, I mean the UI design.
> > As you point out, this can be configured from winecfg. So why do we need
> > a separate mechanism, with an ad-hoc environment variable? Why is it
> > only usable at prefix creation? Is there a way to unify the features, or
> > make them easier to use? How is it different from `winetricks sandbox`?
> > etc. etc.
> > Not sure this is the right place to discuss this, but the problem with winecfg is that the config is stored inside the WINEPREFIX. Every new WINEPREFIX would need to be configured again, since you (currently) can't have a global config. Similar issue with `winetricks sandbox`, you need to remember to do it in every new WINEPREFIX. I'm testing a lot of applications, and they often tend to put files into Documents and similar folders, and I want to prevent that. But since I regularly delete my WINEPREFIX, that config currently can't be permanent.

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/3259#note_52188