https://bugs.winehq.org/show_bug.cgi?id=53453
--- Comment #10 from Anonymous williammpratt81@gmail.com --- WINEPREFIX=~/.wineprefixbug winecfg
The diff is way too big. Unless there is a shell script of some kind, which can be used to automatically minimize the WINEPREFIX configuration directory, there is no way in which I can track this down (without writing such a tool myself, which would involve me probably knowing about the file formats of every single file managed by wine and knowing which files are relevant to begin with (in other words, I'd first have to become a wine expert (something I don't want to be))).
Do you have such minimization tools? If not, why do you people even pretend to offer any kind of compatibility between versions? In a project with many outside contributors potentially messing up something critical and many, many users, surely _someone_ must have thought this can't ever scale, right?
The bug apparently has existed for over a year. Not good.
I think the lesson here is that a single wine configuration shouldn't contain the installation of multiple independent applications, because it becomes a debugging nightmare (because the tools don't exist).
When I run with some empty WINEPREFIX directory, winecfg shows a window with some tabs as it is supposed to do (and asks about the installation of mono). So, it's an absolute certainty that some incompatibility related _only_ to the library resolution of winecfg between 6.01 and 7.13 was introduced.
I don't understand how someone writing a program can make such basic mistakes in the first place and if such a thing happens (because apparently the programmer wasn't as smart as they thought they were) once doesn't immediately provide such bug minimization tools (such tools have been written about for _decades_ and have been part of the "art" for much longer than that).