(5) have any dependency handling for optional packages. Really, this thread boils down to: the Sage library depends on some optional packages. Any kind of hacks around that (like running "sage -b" by hand in scripts) will just lead to race conditions.
On Monday, August 4, 2014 2:58:02 PM UTC+1, wstein wrote: > > (1) Run "sage -b" as part of installing any package that requires it > for the install to finish. Your argument not to run "sage -b" isn't > convincing, because the user is explicitly installing a package > anyways, so they are potentially changing things all over Sage. Or, > > (2) Tell people they have to run "sage -b" clearly in the package > install message. This won't work, because after 20 pages of build > output, nobody is likely to read this. Or, > > (3) Instead of telling the user to reinstall the missing package (in > minisat say), actually give a useful error message, instead of a > totally wrong one. E.g., check to see if the minisat library is > installed, but the cython module isn't built. I don't like this > since it is fragile. > -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
