Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • Thanks. After copying prefix and renaming the copy directory, e.g. to ~/.wine-new, is what remains to do exactlyexport WINEPREFIX=~/.wine-new and wine winecfg? (wiki.winehq.org/…). In production of software engineering, how is rolling done broadly speaking? Commented Dec 13, 2019 at 11:46
  • I read quora.com/…. Rolling upgrade seems to apply only to client-server software. Upgrade server while client of older version is still running. Does this require multiple instances of server and move request to other instance? Does this require the server of new version be compatible with client of old version? (In case of Wine, that is not true?) Does client still need to be upgraded, but can be upgraded only after it voluntarily exit, or not necessarily since the server of new version can work with client of old version? Commented Dec 13, 2019 at 11:53
  • I think I get the idea. I will read more when I have time to. Commented Dec 13, 2019 at 11:58
  • By split upgrades, do you mean the software itself allows client and server with different versions to run together? Is that different from en.wikipedia.org/wiki/Rolling_release? Commented Dec 14, 2019 at 9:33
  • I’ve expanded my answer a little to address your prefix questions, and explain how software can handle rolling upgrades. Rolling upgrades are indeed only a problem when two pieces of software can be upgraded separately, but need to work together (and surprising though it may be, Wine is client-server software). Rolling releases are another matter entirely, releasing and upgrading are orthogonal concepts. Commented Dec 14, 2019 at 9:47