On Mon, Apr 25, 2011 at 2:19 PM, Jason Grout <jason-s...@creativetrax.com> wrote: > On 4/25/11 6:10 AM, John Cremona wrote: >> >> Thanks for the various comments. >> >> I have definitely used cp to copy sage from one place to another >> before, with expected behaviour on first startup. This time I used >> scp for some reason. I just redid it using rsync, following Dave's >> suggestion, and everything is normal. >> > > > "Normal" as in now you see the message about changing hardcoded paths in the > newly-copied version,
Yes. or "normal" as in when you start up the newly-copied > Sage, it just starts up normally without changing hardcoded paths? No. In other > words, should we investigate this further now? > I think not. Let's just assume I had messed something up, though I don't know what -- and using plain cp had always worked fine for me in the past. John > Thanks, > > Jason > > > > -- > 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 > -- 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
