| 1 | | The Unix Filesystem Hierarchy Standard advises '*/lib' as a place for libraries but in version 2.3 allows other '*/lib*' paths. The package install script `configure` thus assumes (maybe not on all systems) that, if no `execdir` is given, `*/lib` should be used. This leads to doctest fails in `dev/sagedev.py` caused by mismatch between GIT_EXEC_PATH in `bin/sage-env` (which hardcodes `local/libexec`) and the actual `execdir` used in the git install (which is `local/lib` on SuSE and other systems if it's not preset with the configure command), introduced with #15901. |
| | 1 | The Unix Filesystem Hierarchy Standard (FHS, http://www.pathname.com/fhs/) advises `*/lib` as a place for libraries but in version 2.3 allows other `*/lib*` paths. The package install script `configure` loads the `site-config` script which on SuSE and other systems assumes that, if no `execdir` is given, `*/lib` should be used. This leads to doctest fails in `dev/sagedev.py` caused by mismatch between `GIT_EXEC_PATH` in `bin/sage-env` (which hardcodes `local/libexec`) and the actual `execdir` used in the git install (which is `local/lib` if it's not preset with the configure command), introduced with #15901. |
| | 2 | |
| | 3 | Solutions are checking for `lib/git-core` or explicitly specifying `configure --libexec="$SAGE_LOCAL"/libexec` in git's `spkg-install`. |
