On Thursday, 21 July 2022 at 11:31:35 UTC-7 Matthias Koeppe wrote: > > 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. > > Right .. but that would require telling the system which libraries need to be preserved ... I guess one could collect the dependencies by a liberal ldd application, but then one would need to query the package manager which packages provide the requisite library files and then somehow register those packages *are* dependencies ... I guess that could be done by building a placeholder package (rpm or deb) that declares all the specific dependencies. And to "declare" these, one could install that package. Upon a reconfigure+rebuild, one could uninstall the old placeholder, recompute the new dependencies, and install a new placeholder ...
Conda looks like it has potential too, provided the " pip install --no-build-isolation -v -v --editable src" can somehow be overlaid with the git-managed repository and have git-trac configuration with it? Then that could make for a reasonable development environment. It's presently unclear to me (but that's probably just inexperience) whether a "production" conda build could co-exist with a "development" conda build: is "conda activate" something local or does it change the global state of conda (e.g., is it possible to have different conda environments activated in different concurrent processes)? -- 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/772a9ff0-4fb6-49a0-8cb6-6dcd97ba3b45n%40googlegroups.com.
