> The only idea I have to deal with this is to copy all of extcode/magma > into .sage/extcode/magma say, and then have sage only use magma code > that's in .sage/extcode/magma/. > Whenever sage is upgraded, the .sage/extcode/magma would have to get > deleted and re-copied, using a facility similar to how the Gap > workspace always gets updated when Sage has been upgraded. Thoughts?
Yeah, that's pretty much what I'd do too. Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://www.informatik.uni-bremen.de/~malb _jab: martinralbre...@jabber.ccc.de --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
