Changes between Version 44 and Version 45 of Ticket #21707


Ignore:
Timestamp:
07/13/20 18:48:35 (17 months ago)
Author:
mkoeppe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21707 – Description

    v44 v45  
    3131
    3232- The goal is to enable downstream sage packagers to use a whole unmodified `src` directory to build and install sagelib.
    33 - Downstream packagers would provide their own "implementation" (one Python module [https://git.sagemath.org/sage.git/tree/build/pkgs/sage_conf/src/sage_conf.py.in?id=1c5d011b5f05a954dd2ea810635c9d59cc48e7b5 sage_conf.py]) of the configuration module defined by #29038, instead of patching sources. They would *not* use the reference implementation in `build/pkgs/sage_conf`, which is intended for use with sage-the-distribution only.
     33   - more precisely, to use the pip-installable source package created by `build/pkgs/sagelib/spkg-src` (#29950); see also #30036       (pip-installable sage)
     34- Downstream packagers could provide their own "implementation" (one Python module [https://git.sagemath.org/sage.git/tree/build/pkgs/sage_conf/src/sage_conf.py.in?id=1c5d011b5f05a954dd2ea810635c9d59cc48e7b5 sage_conf.py]) of the configuration module defined by #29038, instead of patching sources. They would not necessarily use the reference implementation in `build/pkgs/sage_conf`, which is intended for use with sage-the-distribution.
    3435
    3536**Relation to the goal of sagelib as a standalone Python library** (#21507)
    3637
    3738- An sdist of sagelib, intended to be installed from source from PyPI, could package or depend on another implementation of `sage_conf` that calls an autoconf-generated configure script (which reuses parts of the build/pkgs/SPKG/spkg-configure.m4 infrastructure); see #29119.
     39  - for example, by delegating this behavior to a pip-installable package `sage_bootstrap` (#29039)
    3840
    3941**More related tickets:**