Sage-relevant environment variables

[John Cremona]

I have machines I have been building Sage on (and using for development) for 10 years or more, and they have several environment variables of the form SAGE* which I set in my .bashrc script.  I suspect that all or most of these are redundant; some may even be harmful.  Is there a list somewhere of which envoronment variables *are* currently used?

Here's an example:

jec@lehner:~/sage (branch: develop)$ env | grep SAGE
SAGE_MATPLOTLIB_GUI=yes
SAGE_PARALLEL_SPKG_BUILD=yes
SAGE_ATLAS_LIB=/usr/lib

Another also has

jec@atkin:/usr/local/include$ env | grep SAGE
SAGE_UPGRADING=yes
SAGE_INSTALL_CCACHE=yes

John

[Dima Pasechnik]

Of these listed, only SAGE_INSTALL_CCACHE and SAGE_MATPLOTLIB_GUI
are mentioned in Sage's source, as you can see by running

git grep SAGE_MATPLOTLIB_GUI
git grep foobar

etc

> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAD0p0K4is68YT6zb%2B8mrjOiB-86FASFSWj%2B4%2Br%3Din90P8sn18w%40mail.gmail.com.

[John Cremona]

Thajd Dima, very helpful as always!  I can't believe that after years of using git I did not know about git grep (but I'm sure that you can believe it).

Incidentally, setting SAGE_ATLAS_LIB was one of the early ways to help developers by saying to use a system build of atlas which otherwise took a very long time.  We have come a long way since then.

John

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2VifUqRABxL_M1_EPNuA0LTVMbVUzDPP6VmLAf7eNU%3Dg%40mail.gmail.com.