#5852: [with patch, positive review] the detection of SAGE_ROOT in
$SAGE_ROOT/sage
script should expand symlinks recursively (fix this on systems that support
readlink -f)
----------------------+-----------------------------------------------------
Reporter: tornaria | Owner: tornaria
Type: defect | Status: closed
Priority: major | Milestone: sage-4.0
Component: misc | Resolution: fixed
Keywords: | Reviewer:
Author: | Merged:
----------------------+-----------------------------------------------------
Comment(by was):
It's possible that this ticket should be reverted until a major bug it
causes is fixed.
The reason for this ticket in the first place was the following, as given
in the ticket description:
{{{
/home/sage$ md5sum sage-3.4/sage
4153919efe1edcd34ad7fa193122d679 sage-3.4/sage
/home/sage$ ln -s sage-3.4 sage-3.4-symlink
/home/sage$ ln -sf /home/sage/sage-3.4-symlink/sage
/home/tornaria/bin/sage
/home/sage$ type sage
}}}
Notice the symlink of the Sage script
{{{
/home/sage$ ln -sf /home/sage/sage-3.4-symlink/sage
/home/tornaria/bin/sage
}}}
For the record, this is *not* how I meant the sage script is meant to be
used. I bet this isn't documented, but it should be. The script should
never be used that way. Instead one should do
{{{
/home/sage$ cp /home/sage/sage-3.4-symlink/sage /home/tornaria/bin/sage
}}}
and then edit the copied script to explicitly point to the ROOT. It was
never my intention for somebody to run the sage script unmodified outside
of SAGE_ROOT. Me not intending this means that elsewhere in the Sage
build/test system this assumption is made, and the workaround on this
ticket actually seriously breaks things for some users.
The change in this ticket causes serious breakage for people whose home
directory is NFS mounted, and for which their Sage build is on another
volume that is symlinked from their home directory. i.e., this sort of
setup:
{{{
cd ~wstein # my home directory is NFS mounted.
mkdir /tmp/wstein # /tmp is a local disk
ln -s /tmp/wstein sage-build
cd sage-build #
# build sage here, doctesting fails completely
}}}
I'm doing a test build for myself to confirm that this happens, and if so
and I can't figure out how to fix this promptly (maybe I will be able to),
then we have to revert this change, and document that one can't just
symlink the sage script out.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5852#comment:10>
Sage <http://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
-~----------~----~----~----~------~----~------~--~---
