https://bugs.winehq.org/show_bug.cgi?id=45317
--- Comment #15 from Hans Leidekker hans@meelstraat.net --- (In reply to Piotr Caban from comment #9)
I've done much more testing and I think that the correct way is to do a "major upgrade" on every mono update. I think so because of the way how update needs to be installed by the user:
- major upgrade - it's enough to click on the msi file to install the
update, depending on msi file content old version will be preserved or removed
- minor upgrade - has identical user deployment methods as small update
- small update - needs to be installed as patch or complete reinstall, if
you decide to do the minor upgrade new mono versions will need to be installed in following way: msiexec /I wine-mono-4.7.2.msi REINSTALL=ALL REINSTALLMODE=vomus
Most users don't handle these updates directly. I don't think it's too much to ask users who want to test an update to type a few extra characters. We could add an exe wrapper if we really needed a single click installer.
There are also many restrictions regarding what can be done in small and minor upgrade, I don't think you want to pay attention to that on every release.
Don't know about 'many', but you can't modify the feature tree. This hasn't been an issue so far, wine-mono has had a single feature from the beginning. Note that you can still add features and components.
A major upgrade defines a new product, which means that the old product will be removed first. So even if there's a small number of files that have changed (a typical update), all of them will be deleted and rewritten.