Sigh. It seems that in the recent past, I never moved Sage installs after building, whenever I wanted to do development. So whenever I created clones under devel/, the Sage install in question was still in precisely the same place (path), where it had been built. This works fine even with bleeding-edge Sage-4.2!
However (even right after rebooting), if I move a Sage install to some other directory, and *then* do "sage -clone blah", this fails. At least on MacIntel OS X 10.4.11, with Sage-4.2, Sage-4.1.2, and also Sage-4.1.1. As noted above, I only hadn't noticed this before. I have no older Sage installs available anymore, so I can't tell how long this problem already exists. Rationale: Either this is an issue specific to Mac OS X 10.4, then I could live with that. Or this is platform-independent, then nobody has complained (or even noticed) for quite some time, so it is a non- issue. (Moving a Sage install, and then starting Sage, does work fine as usual!) Cheers, Georg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
