#13963: Fix checking for and resetting GAP workspaces
----------------------------------+-----------------------------------------
Reporter: jdemeyer | Owner: GeorgSWeber
Type: defect | Status: positive_review
Priority: critical | Milestone: sage-5.7
Component: build | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers: Volker Braun
Authors: Jeroen Demeyer | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by jdemeyer):
Replying to [comment:7 leif]:
> Minor comments:
>
> * `GAP_BINARY` is misleading, as `$SAGE_LOCAL/bin/gap` is a shell
script.
I think that the name `GAP_SCRIPT` would be even more misleading.
Besides, for this code it doesn't really matter whether it's a binary or a
script, it's only needed to check the time when GAP was installed.
> Avoiding to think of the race conditions we may run into here... ;-)
It mainly depends on how GAP's `SaveWorkspace()` is implemented because
that would be the most obvious place to check for race conditions.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13963#comment:8>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
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.
