On 11/5/19 5:18 AM, VulK wrote: > I am not sure I agree with setting this at build time: a jvm could be > installed afterwards and/or updated independently of sage > S. >
This is generally considered a bad practice because it leads to unpredictability: https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Automagic_dependencies You already have to recompile sage when any of its libraries are upgraded. (And even if you think you use the bundled versions of everything, try upgrading your system's glibc and see what happens.) The only reason java is different is because we half-assed this stuff a long time ago when we decided that java was going to be a kinda-sorta dependency but nobody felt like making an spkg for it. The good news is, as more and more things are unbundled, rebuilding sage during development becomes pretty easy. You only have to recompile the things that need recompiling, which in this case would likely be the one file where jmol is used. The bigger win is for end users, whose package managers can handle all of this stuff for them once our build system is sane and predictable =) -- 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/e410c82b-2a6c-0d23-a77c-5a892350440c%40orlitzky.com.
