Safely handling the renaming of aaa packages?
by redneonglow from LinuxQuestions.org on (#5E341)
I have a Slackware-current VPS which I update every week. I took a look at the Changelog today and saw that on Monday, "aaa_elflibs" was renamed "aaa_libraries" and "glibc_solibs" was renamed "aaa_glibc-solibs".
I'd imagine it would seriously break things if I ran "slackpkg clean-system" either before the new packages were installed (making me unable to run anything) or afterward (since that would remove the contents of the new packages).
What is the safest way to handle removing the old packages? I'm guessing it would be to first run "slackpkg install-new", then "slackpkg upgrade-all", and then remove the aaa_elflibs-... and glibc_solibs-... files from /var/log/packages. Am I wrong?
I'd imagine it would seriously break things if I ran "slackpkg clean-system" either before the new packages were installed (making me unable to run anything) or afterward (since that would remove the contents of the new packages).
What is the safest way to handle removing the old packages? I'm guessing it would be to first run "slackpkg install-new", then "slackpkg upgrade-all", and then remove the aaa_elflibs-... and glibc_solibs-... files from /var/log/packages. Am I wrong?