#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 | Resolution:
Keywords: location pkgconfig | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
--------------------------------------+-------------------------------------
Comment (by leif):
Pinging myself...
In principle, spkgs should properly "initialize" their `.pc` files by
themselves, but analoguous to `sage-make_relative`(?), `sage-spkg` could
do that as well. (I was thinking of moving the code -- of course
rewritten as a simple shell function -- there a long time ago.)
But [regarding the typically endless review process] it's probably easier
to rewrite / enhance the code we have where it is; I do have an editor
window open with that since a couple of weeks, when IIRC Justin once again
ran into and reported this issue on sage-release.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12331#comment:1>
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.
