> > 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?
I ran into something like this once too. I can't quite remember the circumstances, but I think it was something like this: if you copy Sage, rather than moving it, it can't tell it's been copied, because the startup routine just checks that there is a Sage instance at the hard-wired path -- it doesn't check if that Sage instance is the one that's running. -- 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
