#16131: Do not use full-sync for release upgrades, introduce another command
instead
------------------------+----------------------------
Reporter: bitigchi | Owner: nobody
Type: bug | Status: closed
Priority: normal | Milestone: Unscheduled
Component: - General | Version: R1/Development
Resolution: invalid | Keywords:
Blocked By: | Blocking:
Platform: All |
------------------------+----------------------------
Changes (by waddlesplash):
* status: new => closed
* resolution: => invalid
Comment:
Yes, all "full-sync" does is that it synchronizes all installed "provides"
you have with the ones in the repositories. So, for instance, if you have
"gawk" installed, but it was replaced with "gawk_x86" and "gawk" removed
from the repos, "full-sync" will uninstall "gawk" and install "gawk_x86"
instead. Similarly, it will also downgrade packages, etc. whereas "update"
will only take updates, and never downgrade or uninstall packages. So
"full-sync" as the SoftwareUpdater default makes sense, because otherwise
you can get "stuck" when packages that Haiku itself depends on are
replaced/removed/etc., as has happened in the past few months.
In order to change releases, you have to change repositories first to get
the newer packages. If we pushed a new release out in the existing
repositories, but we did not remove any packages, then "pkgman update"
would also upgrade to that; so running "pkgman upgrade" is not actually
protection against a "distribution upgrade", which is a Linuxism we never
really adopted. (It is worth noting that on e.g. Ubuntu, you have to run
"apt dist-upgrade" to get newer kernels occasionally, within a release,
and the GUI package managers usually run "dist-upgrade" always under the
hood.)
--
Ticket URL: <https://dev.haiku-os.org/ticket/16131#comment:2>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
