Comment by noirbot
3 years ago
Sure, I'm not contesting that Wine breaks things with updates. So does a lot of stuff on Linux. The amount of times I run an apt update and some config file is now obsolete or just gone is a lot more often than I'd like.
The advantage is that the Wine Ecosystem seems to realize this more than the Linux ecosystem at large, and specifically makes it easy to pin versions and never update. If it worked, why update? Or why not roll back? I'm already used to having to do that with every other part of linux gaming including my graphics drivers...
> If it worked, why update?
For multiplayer games, which nowadays get updated every day or something, and old versions are incompatible.
I'm not asking why you'd update the game, I'm asking why you'd update Wine if your game "is constantly broken by updates".
It's one thing if the game keeps updating and then you have to hope it works on the same version of Wine or re-find which version of Wine the new version of the game works with, but presumably that's a problem that the OP isn't happening with The Sims 3.
If the game works on a specific version of Wine, why would you mess with it? Or if you are, then treat it like any major OS update and back up/be ready to roll back if it breaks something. Wine is especially good at letting you make multiple sub-environments, so it's not like your whole system has to be on the same version of Wine.
You update Wine to fix game A, and it breaks game B. Or something small is broken in a game, so you try to update to fix it.
1 reply →