Sunday, April 28, 2024
3
rated 0 times [  3] [ 0]  / answers: 1 / hits: 377  / 3 Years ago, fri, july 16, 2021, 11:12:34

I maintain a package on launchpad that releases approx every month. However, our new version is no longer compatible with the previous version, because of some fundamental changes. So version 2.8 should not be upgraded to 2.9. I specifically want to prevent users from upgrading to 2.9 by mistake. Instead if they want to upgrade, they should be forced to apt-get remove, and then apt-get install to get a fresh install.



Is there a way to specify this in the package description? Or am I better of creating a separate repository or changing the name of the package?


More From » package-management

 Answers
7

You should change the package name. Not only because there is no good way from your end to prevent an upgrade, but more importantly because users may want to have both versions installed during a transition period. E.g. install the new version, run it on test data for a while, then do the difficult data migration when they've stabilized the new configuration.



Historical example: Apache (I don't remember if Ubuntu had separate Apache 1 and Apache 2 at some point, but Debian definitely did).


[#40998] Saturday, July 17, 2021, 3 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
arsleyeuth

Total Points: 72
Total Questions: 121
Total Answers: 112

Location: North Korea
Member since Mon, Oct 31, 2022
2 Years ago
;