I'm pretty sure that if a package has been "dnf install"-ed, then it's considered desired, and not just there as a prerequisite. So preventing libraries from being removed should be as simple as including the requisite package in the recommended "dnf install ..." as written at:
https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation (it's probably good if that gets updated with "dnf" instead of "yum" -- that change happened around 2015!) On Wednesday, 20 July 2022 at 13:59:07 UTC-7 Matthias Koeppe wrote: > On Wednesday, July 20, 2022 at 1:55:52 PM UTC-7 Matthias Koeppe wrote: > >> On Wednesday, July 20, 2022 at 1:42:58 PM UTC-7 Nils Bruin wrote: >> >>> I've noticed that after a modest upgrade (just "dnf update"), with some >>> regularity sage breaks. In the most recent edition, "libflint.so" couldn't >>> be found. >>> >>> I guess there is some prerequisite that sage was relying on to be >>> provided by the operating system was changed? >>> >> >> When system packages no longer need a specific old version of a shared >> library, then the system package manager may remove that version. >> It does not know about user-built programs that link to system libraries. >> That's not Sage-specific. >> >> Perhaps there is a way to stop dnf or other package managers from >> removing unused library packages? >> That would be worth investigating. >> > > > https://www.reddit.com/r/Fedora/comments/3pqrv9/dnf_remove_package_keep_dependencies/ > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/539338ec-2b92-4d05-b2d5-05e29e59f6bbn%40googlegroups.com.
