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,
though. The review instructions are a bit touchy, since the patch needs
to be applied before the sage is moved.
Can someone please review this patch? It would make reviewing and
installing spkgs a lot easier, as they actually build and refer to the
correct paths. It may also fix some longstanding bugs where sage picks
up system packages when it should pick up sage-specific packages.
To review, this should be sufficient:
1. Download and build Sage (important; it must be a fresh build from
source).
2. Apply the patch at the ticket to the scripts repository (in
SAGE_ROOT/local/bin):
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/9210/trac-9210-rewrite-sage-location.patch
3. Delete the file SAGE_ROOT/local/lib/sage-current-location.txt, if it
exists
4. Now run Sage, then exit (this updates the sage-current-location and
pkgconfig files appropriately).
5. Move the sage directory and run Sage again. The
SAGE_ROOT/local/lib/sage-current-location.txt should be updated, and the
pkgconfig files in SAGE_ROOT/local/lib/pkgconfig/ should also be updated
to the new path (you can check the freetype2.pc file, for example, to
see the new sage directory is listed there in the SAGE_ROOT variable).
Many thanks to whoever reviews this!
Thanks,
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
