On Wed, Aug 26, 2009 at 7:16 AM, Tim Lahey<tim.la...@gmail.com> wrote: > > > On Aug 26, 2009, at 2:54 AM, Robert Bradshaw wrote: > >> >> Any thoughts on how this would impact having multiple versions of >> Sage on the same machine? What about being able to move them around/ >> delete them? >> >> - Robert > > > New frameworks generally live in /Library/Frameworks, although I expect > that ~/Library/Frameworks is a possibility too. Multiple versions of > Sage wouldn't be a problem. Upgrading can keep the previous version > around and set new symlinks to point to the Current version. This > approach > is there because it allows one app build against a specific version to > still work when updated. Deleting old versions is fine, deleting the > most recent version would require fixing the Current symlinks. >
Wait, so is a key point that if one builds Python for Sage as a framework, then Python is no longer contained in SAGE_ROOT/local/? Is that what you're saying? I can see numerous problems and confusion arising as a result. Hopefully it can still be in SAGE_ROOT/local, and maybe there is a symlink? William --~--~---------~--~----~------------~-------~--~----~ 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 URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
