> Craig: thanks for pointing out SAGE_CHECK. But it strikes me that > there is no way I can run those tests now, without recompiling the > corresponding spkgs from scratch. Is there any way one can get spkgs > to provide a test script, separate from the installation procedure, so > something like "sage -tspkg flint-xxx.spkg" would run the tests for > Flint?
Many packages don't build test suites unless you ask for them. (I know flint is this way; building the test suite takes about as long as building the library.) So we'd need to build test suites all the time, and store the test suites for later use, which I believe is different from what we do know: we delete all the build remnants. You might find the spkg-check file in the .spkg file useful. Nick --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
