Hi,
A long, long time ago I wrote this sage-location script, which is
meant to be run when you move Sage. It hacks around certain
hard-coded paths, and of course isn't the optimal solution to
anything. But it tends to work. It's 100% designed for binary
distribution of Sage.
In practice I personally *never* ever move -- I build it in place and
that's it. However, I very frequently see the following with Sage
installs that have never once moved from their original home:
Forcing sage-location, probably because a new package was installed.
Updating various hardcoded paths...
(Please wait at most a few minutes.)
DO NOT INTERRUPT THIS.
This is a somewhat disturbing waste of time, right?
-- William
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
