Opened 3 years ago

Last modified 7 weeks ago

#21707 needs_review enhancement

Split sage-env into sage-build-env and sage-env — at Version 2

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-8.9
Component: build Keywords:
Cc: embray, jdemeyer, leif, fbissey, dimpase Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description (last modified by mkoeppe)

sage-env is used by both Sage-the-distribution while building packages, and by Sage at runtime.

It should be split into two or three separate scripts.

  • sage-build-env is for the build-time environment variables for sage-the-distribution, should go into build/bin and not be installed. Or perhaps more stuff should be put into build/make/install
  • sagelib-build-env is for the build-time environment variables for sagelib
  • sage-env is for the run-time environment variables of sage and should be installed by src/ (thus very late in the build process), rather than by build/make/Makefile. (sage-env` will be very short and at some point hopefully disappear, if we want sagelib to become a standalone Python library - #21507)

This is a step towards the cleaning of src/bin as described in #21569, #21570, #21559.

Change History (2)

comment:1 Changed 3 years ago by fbissey

One comment. Currently sage_setup is installed because it needs to be installed to be doctested - like the rest of sage. But nothing in sage_setup is really needed at runtime and distro can choose not to install it. I don't in sage-on-gentoo. I tend to push for thing not needed at runtime to be moved in there. And that's where I would have put sage-build-env but I am not going to fight it going into build/bin although I'd like everything used by to be neatly under src.

comment:2 Changed 3 years ago by mkoeppe

  • Description modified (diff)

Thanks - I've updated the description

Note: See TracTickets for help on using tickets.