In <firstname.lastname@example.org>, on 03/10/21
at 12:58 PM, "Massimo S." <email@example.com> said:
>which package should i updated from the ANPM utility?
>please give me the list to be on pair with your environments
>(i guess i've to go to the "available" menu and install the last updates
>that you will give me the list)
I may not be the best person to ask because my systems are not typical.
For your purposes since we are talking about a production system, I
recommend updating because you need to, not just because an update is
available. Updates exist to fix problems, but if you are not experiencing
the problems the update fixes, installing the update is not likely to
provide you any immediate benefits and regression do happen.
For example, if you are getting traps in an older release of libcn0 or the
release you are running is missing a required entry point for some update
app, it's time to update the libc package and anything it requires.
I recommend you learn to use the ANPM Yum tools package export feature. I
keep timestampped copies of the exported package list. This makes it
relatively easy to decide what needs to be backleveled if non-obvious
problems start to occur.
Paul's builds tend to use a small subset of the available packages -
generally libc, libcx and pthreads. You will probably find you need to
keep these updated so that you can run Paul's current builds.
The corollary is that ANPM can install a large number of packages that you
will never use because you are not using any of the applications that
require these packages.
In general, you probably want to avoid packages from the experimental
repository. There are time when they are needed, but it's best to need
them before installing them.