Changes between Version 2 and Version 6 of Ticket #16350
- Timestamp:
- 05/14/14 04:27:28 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #16350
-
Property
Summary
changed from
GIT_EXEC_PATH doesn't match installed git execdir
toon some systems, pkg-libexecs are installed into local/lib instead of local/libexec
-
Property
Summary
changed from
-
Ticket #16350 – Description
v2 v6 1 Doctest fails in `dev/sagedev.py` caused by mismatch between GIT_EXEC_PATH in `bin/sage-env` and `execdir` in the git install, introduced with #15901. 2 3 `GIT_EXEC_PATH="$SAGE_LOCAL"/libexec/git-core && export GIT_EXEC_PATH` while `execdir` is `local/lib`. 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.