Not sure what you mean with "is that because"....but I may guess what you mean...asqwerth wrote: Sun Oct 06, 2024 11:22 pm@fehlix , is that because MX-Updater's full upgrade or non-full upgrade choices are set out in the $HOME/.config//MX-Linux/apt-notifier.conf file as well as in MX-Updater's GUI preferences?
If my config file is:
and my upgrade preference is:Code: Select all
# Use alternative apt/apt-get command line package manager use_nala = true
ksnip_20241007-111836.png
will that automatically make any MX-Updater upgrade via nala a full upgrade?
MX Updater, ignores the nala.conf settings in resp. to full-upgrade and always
uses explicitly for "basic upgrade" nala's "upgrade --no-full" (which is apt/apt-get upgrade)
and for "full upgrade" nala's "upgrade --full" (which is apt/apt-get full-upgrade).
So, whatever the user/admin has set within nala.conf will be ignored with MX Updater,
hence I wrote "With MX-Updater: No"
Background:
nala uses "commands" like "upgrade" and has options for those command like "--full" and "--no-full"
Around version 0.14 they introduced a new "command" "full-upgrade",
in order to make it look similar to apt. But at that time they found out,
that they have now both commands "full-upgrade" and "upgrade" doing the same thing when having default upgrade-option set to --full.
And to reduce the confusion, they reverted the default "upgrade" option back to --no-full.
So, MX Updater ignores nala's self made "confusion" and uses always what was selected with the MX Update's preferences either basic upgrade or full-upgrade.