trouble with sage_started.txt
Closed this issue · 4 comments
some file, sage_started.txt is falling on our feet in #15105.
the file is created by the build process in SAGE_ETC, which possibly is not writable at that time.
also, the file seems to have something to do with the first run of the sage script. the first run must be possible to happen before installing anything (such as in make check).
it seems that we need a sort of wrapper to implement a functional pre-install sage. this wrapper could also handle sage_started, or disable the mechanism.
CC: @jdemeyer @kiwifb @mkoeppe
Component: build
Issue created by migration from https://trac.sagemath.org/ticket/21510
What exactly is the problem to be fixed here? "foo is falling on our feet" is not very descriptive. You really need to give more details. Also, when you say things like "SAGE_ETC, which possibly is not writable at that time." you should justify that.
Description changed:
---
+++
@@ -5,5 +5,3 @@
also, the file seems to have something to do with the first run of the `sage` script. the first run must be possible to happen before installing anything (such as in `make check`).
it seems that we need a sort of wrapper to implement a functional pre-install `sage`. this wrapper could also handle sage_started, or disable the mechanism.
-
-(component should be "sagelib" but that is missing in the drop down. choosing "build").The description should be clarified to distinguish the following issues:
- What is
sage_started.txt? - Does it belong into
SAGE_LOCAL(=$prefixby #21479) or rather into the build directory (SAGE_ROOT, distinguished in VPATH builds (#21469) from SAGE_SRC_ROOT)? - If it does belong into
SAGE_LOCAL, then ifSAGE_LOCALis only root-writable, then SAGE_SUDO needs to be invoked (#21537). - Beyond that, any discussion of "separating
makeandmake install" should please go to ticket #21495, not here.
Closing because the issue isn't clear and no reply was given by the submitter after ample time.