What's the use case for configuring folders individually?
TBH, I just need all of them at once. But I figured I could also just make it fully configurable just in case someone needs that. I didn't see any harm in making it fully configurable from the start, just in case.
How are we going to ensure that prefix updates to the right thing?
Sorry, I don't understand what you mean. Mind elaborating? The logic only runs when the folder doesn't exist. Unless I missed something, updates shouldn't be a problem.
How can it be enabled/disabled after prefix creation?
The logic I changed only runs when the folder doesn't exist, you can always link/unlink the folders using winecfg.
How is it going to handle inability to open Unix files (fonts etc.)
Well, it's not different from disabling the Z:\ link in winecfg. If someone doesn't know what they're doing, they can run into problems with that as well. This MR would only add on option to disable the link automatically when creating a new WINEPREFIX.
This needs a lot more thought and a proper design.
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?
-
Fabian Maurer (＠DarkShadow44)