New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sage.env: Give values from sage_conf precedence over environment variables #34236
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
I am a bit dubious when I see the title. I don't think you should override environment variables unless you absolutely have to. What I think the ticket is about, and feel free to correct me, is that some variables, needed for sage's own operation, should be internal to sage and not exposed to be modifiable by environment variables. They should be private. If my interpretation is correct we need to start with a list of those variables that should be private. |
comment:3
Replying to @kiwifb:
Well, that's a slightly stronger form than what I've written. In what I wrote, the value would still be taken from the environment if it is not defined in The stronger form would be fine for me as well. |
comment:4
Thanks for the clarification. I guess from the point of view of what I have written, that makes all variables in From my distro point of view that may mean adding variables there that I did not care to have. Like |
comment:5
The stronger form can be implemented by just adding
|
comment:6
Some variables such as |
comment:7
When you say in |
comment:8
Replying to @kiwifb:
Yes
It's set in the |
comment:9
So, are you also wanting to cut some redundancies as part of the ticket? I guess it may make sense with some item. |
comment:11
Replying to @kiwifb:
Well, many environment variables set in But by using New commits:
|
Commit: |
comment:12
Replying to @mkoeppe:
Agree on the uselessness. sage-on-gentoo is |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This change will make installations of Sage more robust.
Currently,
will give
SAGE_ROOT_A
(bad), whereaswill give
SAGE_ROOT_B
(good).Similarly to
sage-env
,sage-build-env
: No longer allow environment variables CC, CFLAGS, ... to override configured variables)CC: @jhpalmieri @kiwifb
Component: refactoring
Branch/Commit: u/mkoeppe/sage_env__give_values_from_sage_conf_precedence_over_environment_variables @
4d20b92
Issue created by migration from https://trac.sagemath.org/ticket/34236
The text was updated successfully, but these errors were encountered: