Comment by John Palmieri for The script at $SAGE_ROOT/local/bin/sage-env sets...
Note also that sage-env is in SAGE_ROOT/spkg/base, so it is there right at the start of the Sage installation.
View ArticleComment by kcrisman for The script at $SAGE_ROOT/local/bin/sage-env sets the...
Okay, this at least clears up most of what I wanted to know. @benjaminfjones, can you add that info to the main answer so that others could find it more easily?
View ArticleComment by kcrisman for The script at $SAGE_ROOT/local/bin/sage-env sets the...
What would the difference between this and `sage -sh` be?
View ArticleComment by benjaminfjones for The script at $SAGE_ROOT/local/bin/sage-env...
Essentially, sage -sh calls your shell (say /bin/bash) with an option to prevent loading of the user's .profile or .XXXrc file (for /bin/bash it runs the shell without sourcing .profile, .bash_profile,...
View ArticleAnswer by benjaminfjones for When is ./sage -sh NOT supposed to work? That...
The script at `$SAGE_ROOT/local/bin/sage-env` sets the shell environment up for building spks's. Here's what it reads at the top:...
View ArticleComment by kcrisman for When is ./sage -sh NOT supposed to work? That is,...
Oh, I think nearly ALL of them do! That's in the standard error message when an spkg fails to build.
View ArticleComment by John Palmieri for When is ./sage -sh NOT supposed to work? That...
Which spkgs give these messages? If they really need "sage -sh" to work, then they should be changed so that they have the scripts spkg as a prerequisite in SAGE_ROOT/spkg/standard/deps.
View ArticleWhen would sage -sh not work?
When is `./sage -sh` NOT supposed to work? That is, where should this work in the spkg build process? My sense is that it should work almost immediately - even before Python, right? - but sometimes I...
View Article
