On 9/9/10 5:51 PM, Dr. David Kirkby wrote:
On 09/ 9/10 09:07 PM, Jason Grout wrote:
Currently, installing packages on a Sage that has been moved from its
original build location is seriously broken. The problem is that the
pkgconfig files (which many spkgs use to set up the include paths) are
not updated to the new location.
There is a patch at #9210 that fixes this. It needs to be reviewed,
<snip>
Many thanks to whoever reviews this!
Thanks,
Jason
I have done - it simply does not work for me.
I noted on the trac ticket that you skipped step 4 (running Sage before
moving the directory). Could you please try it again?
As I note on the trac ticket, I think 'sed' may be the best tool for
this, not Python.
That may be. There is more that goes on in this sage-location script,
so python may be better-suited over all. And I'm more confident in
python than in sed. And I'm pretty confident that the current patch
works (if the instructions are followed for reviewing it).
That sed, if someone wants to go ahead and write a sed script, we'll
just go with whatever they seys. :).
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
