Changes between Version 43 and Version 44 of Ticket #21707


Ignore:
Timestamp:
06/09/20 05:52:46 (18 months ago)
Author:
mkoeppe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21707 – Description

    v43 v44  
    16162./3. Obtain sagelib's build-time configuration such as `src/setup.py`'s `library_dirs` and runtime information (`sage.env`) from `sage-config` (introduced in #29038).
    1717  a. In `src/Makefile`, poison the `SAGE_LOCAL` variable.
    18   b. Pass `SAGE_PKGS` (if still needed at all - see #28815) via `sage-config` instead of from `src/Makefile`.
     18   - #29411: make sagelib a script package
     19   - #29779: `pkg-config` installed from SPKG `pkgconf` should not depend on environment variable `SAGE_LOCAL`
     20  b. Pass `SAGE_PKGS` (if still needed at all - see #28815 or #29705) via `sage-config` instead of from `src/Makefile`.
    1921
    20223./4./5. Using `sage_conf` (Python module and script `sage-config`, #29038), make `sage.all` fully functional when imported from a Python, without setting any environment variables (`sage-env`).
    2123a. Initially, phase out `src/bin/sage-env-config` by using `sage-config` instead.
    2224   - #29384: Clean up `src/bin/sage-env-config.in`: Move logic to `src/bin/sage-env`, move non-environment configuration variables to `sage_conf.py`
     25   - #29825: Clean-up for src/bin/sage-env
    2326b. Set `sage.env` variables via the Python module `sage_conf` instead of relying on information from environment variables. Example: `CYSIGNALS_CRASH_DAYS`
    2427c. Set environment variables that are needed only by subprocesses invoked by sagelib in the environment of these subprocesses, rather than relying on them begin set in `sage-env`. This environment could be provided by a variable `sage_conf.SAGE_SUBPROCESS_ENV` and/or more invidual variables. Example: `R_PROFILE`