#5852: The detection of SAGE_ROOT in $SAGE_ROOT/sage and local/bin/sage-env
should
expand symlinks recursively
-------------------------------+--------------------------------------------
Reporter: tornaria | Owner: jdemeyer
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.7.2
Component: distribution | Resolution:
Keywords: | Work_issues:
Upstream: N/A | Reviewer:
Author: Jeroen Demeyer | Merged:
Dependencies: |
-------------------------------+--------------------------------------------
Comment(by jdemeyer):
Replying to [comment:25 leif]:
> Replying to [comment:20 jdemeyer]:
> > I also noticed that `data/extcode/sage/ext/mac-app/start-sage.sh` has
its own `SAGE_ROOT`-detecting code but it probably shouldn't and should
use `sage-env` instead.
>
> It seems the MacOS X app wants just the opposite, i.e. to '''not'''
resolve symbolic links, since the absolute, canonicalized path may
frequently change.
>
> Therefore it always creates (on start-up) the same, "constant" symbolic
link from `/tmp/sage-mac-app` to the current, volatile `$SAGE_ROOT`, which
can only work if the application is also actually ''always'' built in (a
real directory) `/tmp/sage-mac-app/` (such that no change of hardcoded
paths is necessary).
The question is: why are things done this way? It seems to me that the
`/tmp/sage-mac-app` symlink is an ugly hack around a problem which can
probably be solved in a better way.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5852#comment:26>
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.
