#16350: on some systems, pkg-libexecs are installed into local/lib instead of
local/libexec
-------------------------------------+-------------------------------------
       Reporter:  rws                |        Owner:
           Type:  defect             |       Status:  needs_review
       Priority:  critical           |    Milestone:  sage-6.3
      Component:  scripts            |   Resolution:
       Keywords:  environment, git   |    Merged in:
        Authors:  Ralf Stephan       |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  
u/rws/on_some_systems__pkg_libexecs_are_installed_into_local_lib_instead_of_local_libexec|
  51216ea7716e7ad2b150e676760840c947183164
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------
Changes (by {'newvalue': u'Ralf Stephan', 'oldvalue': ''}):

 * status:  new => needs_review
 * author:   => Ralf Stephan


Old description:

> 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.

New description:

 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.

 Solutions are checking for `lib/git-core` or explicitly specifying
 `configure --libexec="$SAGE_LOCAL"/libexec` in git's `spkg-install`.

--

--
Ticket URL: <http://trac.sagemath.org/ticket/16350#comment:12>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to