#12331: updating an spkg may render Sage non-relocatable
--------------------------+-------------------------------------------------
Reporter: jhpalmieri | Owner: leif
Type: defect | Status: new
Priority: minor | Milestone: sage-5.0
Component: scripts | Keywords: location pkgconfig
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
--------------------------+-------------------------------------------------
Here's an issue possibly arising from #11760: suppose you
- build and run Sage, so sage-location has been run.
- then install a new spkg, say python or gsl, which creates a file in
local/lib/pkgconfig
That newly created file never gets initialized by sage-location, so it
doesn't have a definition of SAGE_ROOT in it, so it never gets updated.
So the resulting Sage build might not be relocatable. This is related to
these comments in the `sage-location` script:
{{{
# There's no definition of SAGE_ROOT in the .pc file at all.
# This should never happen, unless the user modified the file.
}}}
and
{{{
# We could of course call initialize_pkgconfig_file(filename)
# here instead to fix this issue, but unfortunately there's no
# such function (for a single file) [yet].
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12331>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
