On Apr 25, 3:39 am, John Cremona <[email protected]> wrote: > It always used to be the case that if you moved the entire Sage build > tree to another place, the first time you ran Sage from the new place > it issued a warning to wait a while while it updated some hard-wired > paths, Has anything changed to make this no longer be necessary? > > I just moved a fresh build in this way (using scp -pr, though source > and destination were local) and the first time I run Sage from the new > location is starts up normally.
I can't reproduce this. Have you actually moved anything? > > [The reason for doing this at all is that I want to test installing > various new spkgs, and I don't think the clone procedure is up to > that, so I just copy en entire unaltered build and work on that.] > > John -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
