I ran into the following scenario: A multi-user machine running a rather old but still supported linux distribution that doesn't have sufficient prereqs to build and install sage from source: I tried sage-the-distribution, but while "bootstrap/configure" succeeded, gmp didn't want to build, probably due to gcc being outdated.
So at that point I figured trying conda would be worthwhile. Because conda is *designed* to work around lack of admin privileges, it is actually not so clear from the instructions how to use conda to install a piece of software for multi-user usage. It's quite doable to get conda to put their install director in a location that is not in a homedir, but conda *really* wants to write stuff into your .bashrc (and obviously, I wouldn't want every user to have to do that!) However, it seems like with the conda install completed, /opt/sage/miniforge3/envs/sage/bin/sage seems to start sage just fine, even without setting up the required conda environment. It looks like the normal "sage" setup seems to do enough: after "sage -sh" I'm getting from "gcc -v" the conda-forge gcc rather than the outdated "gcc". I'd imagine there may be a way of generating a sage start-up script that would properly set up the conda environment before running sage, but as far as I've tested, that's not even necessary. It's a very quick way for getting sage installed, so perhaps there's merit to getting a scenario like this more properly documented/supported. -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/6a3f1912-e7cb-425f-93a5-75df81c09072n%40googlegroups.com.
