On Thursday, July 21, 2022 at 11:14:13 AM UTC-7 Nils Bruin wrote: > On Wednesday, 20 July 2022 at 23:33:09 UTC-7 Antonio Rojas wrote: > >> >> They are not, that's exactly the point of library soversions. The >> soversion, if correctly used, is bumped when a release contains some ABI >> incompatible change that requires a rebuild of consumers. So you can't just >> link to the .so symlink, that would just defeat the point. >> > > Ah boy, that explains why packaging binary software for linux > distributions is such a complicated task. For binary distributions, even > FC36 isn't a stable target! Is that a Fedora-specific disease or do other > distribution just push ABI-incompatible changes within a release as well? A > binary distribution really does need to include all libraries. >
You really just need to stop your distribution from automatically uninstalling the old shared library packages when you do upgrades. Both the old version (needed for your from-source installation of Sage) and the new version (needed as dependencies of upgraded system packages) can coexist in your system. development requires to have two installs: one "production" version, > possibly the OS-packaged one [that might as well be binary] and one > built-from-source one that should either be properly sandboxed in an > environment where the prerequisites are ensured to be stable or where one > accepts that arbitrary rebuilds (including a distclean build) may be > necessary. > Definitely. Basically, don't bring a random development build to the classroom. -- 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/ccc42f2f-8860-4dcf-b4ad-860a02e5de60n%40googlegroups.com.
