As suggested by Max Horn.
This exists since gap 4.10 and will only run the install checks once
while also exiting with an appropriate exit code. This new check has
uncovered some test failures, which are harmless and actually disabled
in a future gap release. The error-detection code for the previous test
target was probably broken.
Two reasons for this:
- more fine-grained space/functionality tradeoff
- preparation for the sage 8.6 update, which finally doesn't need a
downgraded gap anymore but does break when unexpected (non-standard)
packages are installed. Details: https://trac.sagemath.org/ticket/26983
The proper way to deal with gap packages would be to create a package
set, package each one individually and have something like gap
equivalent of `python.withPackages`. I am not willing to do that
however.
There are some starts of a `make install`, but nothing complete yet.
Upstream now ships a `libgap` as a replacement of the custom one used by
sagemath.
Timo Kaufmann
Michael Reilly
R. RyanTM
volth
Guillaume Maudoux
Chris Jefferson
Joachim Fasting
Eelco Dolstra
Peter Simons
Mateusz Kowalczyk
Michael Raskin