Changes between Version 12 and Version 25 of Ticket #16350
- Timestamp:
- 05/14/14 10:42:31 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #16350
-
Property
Status
changed from
needs_review
topositive_review
- Property Cc SimonKing added
-
Property
Reviewers
changed from
to
Simon King
-
Property
Commit
changed from
51216ea7716e7ad2b150e676760840c947183164
toe51b496d83b9bd57b57ed538d65f3281ddb3379f
-
Property
Status
changed from
-
Ticket #16350 – Description
v12 v25 1 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 2 3 Solutions are checking for `lib/git-core` or explicitly specifying `configure --libexec="$SAGE_LOCAL"/libexec` in git's `spkg-install`. 3 Solutions are checking for `lib/git-core` or explicitly specifying `configure --libexecdir="$SAGE_LOCAL"/libexec` in git's `spkg-install`. 4 5 We do the latter here.