#5041: make it so the magma .sig files in extcode don't get written there by
magma
------------------------+---------------------------------------------------
Reporter: was | Owner: was
Type: defect | Status: new
Priority: blocker | Milestone: sage-3.3
Component: interfaces | Keywords:
------------------------+---------------------------------------------------
If one installs sage sytem wide, and a user tries to run any magma
commands, and the .sig files aren't written in data/extcode/magma, then
BOOM! This is a total show stopper for any "normal users" to use the sage
magma interface for anything serious. This must be FIXED!
To fix this, when the magma interface is first run, make sure to copy the
.m files over to $DOT_SAGE/magma first and load from there. One will
have to do the copy the first time the magma interface is started in any
magma session. alternatively, one could try: except: the magma.load
command, and if it fails, then try to copy and load from /tmp/, say or
DOT_SAGE/temp/. Maybe the second idea is cleaner.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5041>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
