We extend the sage_bootstrap package to add the commands:

• sage -package list --output=install-requires PACKAGES... (for sagelib: Generate pyproject.toml and setup.cfg [install_requires], requirements.txt, Pipfile, and src/Pipfile #30913)
• sage -package list --output=requirements PACKAGES...
• sage -package list --output=pipfile PACKAGES...
• sage -package list --output=debian PACKAGE... etc. (taking over the functionality of the shell script build/bin/sage-get-system-packages.)

They generate text output in the format of setup.cfg [options] install_requires=, requirements.txt, and Pipfile; or a list of system packages

bootstrap can use these commands to generate these files for build/pkgs/sagelib/src/ or src. They are deleted by make bootstrap-clean.

References:

• https://pip.pypa.io/en/stable/user_guide/#requirements-files
• https://pipenv-fork.readthedocs.io/en/latest/advanced.html
• https://packaging.python.org/discussions/install-requires-vs-requirements/
• https://pypi.org/project/install-requires/

CC: @seblabbe @dimpase @embray @vbraun @kiwifb @tobihan @tobiasdiez

Component: build

Keywords: sd111

Issue created by migration from https://trac.sagemath.org/ticket/29041