#5254: [with patch, needs work] Mac app bundle: check for relocation at startup
since the bundle version does not trigger the move check
--------------------------+-------------------------------------------------
Reporter: mabshoff | Owner: mabshoff
Type: defect | Status: new
Priority: critical | Milestone: sage-3.4.2
Component: distribution | Keywords:
--------------------------+-------------------------------------------------
Comment(by GeorgSWeber):
Hi Justin, thanks for the comments!
Having slept over them, I feel a bit at a loss, however:
1, 2) I have seen "lisp.run" threads (via the OS X "activity monitor")
only during doctests, or when Maxima was somehow started explicitly or
implicitly during a Sage session. I have no clue how the "app" mechanism
is related to the crashes you see. Perhaps an "exit" command at the end of
the script might help, but this is wild guessing, and right now I don't
have the time to poke around.
3) Incorrect. The script itself is the "app" script that starts Sage up,
so has to be called itself every time. And as for checking whether the
Sage app has moved, we have to call the "sage-location" script every time,
too --- or double somehow its content. How should we know that the Sage
app has moved without checking whether it has moved? And checking this is
exactly what the "sage-location" script does, so there. (Why reinvent the
wheel?)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5254#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
