Upgrading to a new version - what about uninstalled programs? [Solved]

[andymx]

I would like to ask the following. When the time comes to install a new MX version, what will happen about programs that came already installed with my current version that I may have uninstalled? For example, say I uninstall catfish. When a new MX version is to be installed, would catfish be automatically installed again if it's on the new version's ISO?

I'm currently using MX v.23.

[dolphin_oracle]

Yes you get whatever is on the iso.

[gimcrack]

Full Package List: MX Linux 23

https://distrowatch.com/table.php?distr ... 23#pkglist

[MXRobo]

To add with gimcrack:
https://repology.org/repositories/statistics Search MX
https://mxrepo.com/
per viewtopic.php?p=747254#p747254

[andymx]

Thank you very much. Since I'm keeping very detailed notes about the customization that I do on my MX installation, I'll add notes on what I've uninstalled too. This way it will be easy to revert to what I need when I change to a newer version.

[MXRobo]

@andymx I assume that you're aware of MXPI>Enabled Repos - - user-installed-packages, and unlike Windows (I think????), an for a tautology - the iso contains what it contains and has no interaction with the existing distro, unless you're upgrading migrating from say MX-21.3 to MX-23, but even then it's not an interation, but more of a partial preservation process of the existing system – in laymans terms, if I understand it correctly.

MXPI>Enabled Repos - - user-installed-packages

[andymx]

I was referring to upgrading from one version to another, where I uninstalled a program that was on the former ISO installation. I was wondering if the upgrade would recognize that the program was missing from my installation and not install it from the new ISO. Apparently, not so, but it's no problem for me. I'll simply uninstall such programs again after the upgrade.

[MXRobo]

Re, "I was referring to upgrading from one version to another", yes, that's what I inferred from your original post, "When the time comes to install a new MX version", i.e. installing MX-23 when MX-21.3 was previously installed (not an actually migrating, which is the term that I should have used in post #6.

I just meant that app will help when installing a newer iso but to run it on the old version first.

[asqwerth]

I was referring to upgrading from one version to another, where I uninstalled a program that was on the former ISO installation. I was wondering if the upgrade would recognize that the program was missing from my installation and not install it from the new ISO. Apparently, not so, but it's no problem for me. I'll simply uninstall such programs again after the upgrade.

(1) When you do a fresh install of the new MX from a live iso, you basically copy over whatever is preinstalled on the new MX as presented on the iso.

HOWEVER, because of the antiX live system that we use, you can make changes to the live iso you are running, eg uninstall existing programs, install new ones, configure everything the way you want, etc, and then install the live system, as modified, to your machine, using the "Save Live desktop changes" from within the installer.

(2) If you are thinking of doing an in-place upgrade of your old MX system to your new one (migration) -- which is not officially supported and which the dev team warns should only be for more proficient users of Linux/Debian -- then of course an upgrade won't install back applications you removed, since it is upgrading whatever packages are left on your system (subject to installing additional packages listed as dependencies to the packages you are upgrading). Example, MX comes with Firefox. You removed Firefox and are using another browser. If you do an iin-place upgrade of your MX system, Firefox is not going to magically reappear on your system even though it is the default browser found on the live iso of the new MX.

[andymx]

@asqwerth Thank you for a very comprehensive description of the options. You can count me in the group of not proficient users of Linux/Debian, hence I'll not be adopting the second alternative.