#11926: "make build" should run Sage once
------------------------+---------------------------------------------------
Reporter: jdemeyer | Owner: GeorgSWeber
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.7.3
Component: build | Keywords: Makefile build sage-starts
Work_issues: | Upstream: N/A
Reviewer: | Author: Jeroen Demeyer
Merged: | Dependencies:
------------------------+---------------------------------------------------
Changes (by jdemeyer):
* status: needs_review => needs_work
Comment:
Replying to [comment:34 jhpalmieri]:
> Either that, or there needs to be a different test in the Makefile to
decide whether to run sage-starts.
How about having a ''third'' file besides the existing `sage-flags.txt`
and `sage-current-location.txt`? Say, a file `sage-started.txt` whose
existence means Sage was run at least once successfully.
I think we could also use the non-existence of this file as a trigger in
`sage-location` to force some actions. For example, on upgrading, even if
the Sage tree was not moved, it might make sense to call
`update_library_files()` and `update_pkgconfig_files()`.
I would write the file `sage-started.txt` in `sage-location` and
potentially delete it in `sage-starts` (that's what you proposed for
`sage-flags.txt` instead).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11926#comment:35>
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.
