Add debian/fedora/arch/conda package information to build/pkgs, generate Dockerfiles and installation help; add tox.ini

[mkoeppe]

https://doc.sagemath.org/html/en/installation/source.html#linux-recommended-installation
gives apt-get install and yum install command lines to install system packages that will be recognized by build/pkgs/SPKG/spkg-configure.m4.

Several packages are missing, see comments in
https://github.com/sagemath/sage-prod/files/10659286/Dockerfile-ubuntu-minimal.gz

This ticket puts this information on a per-package basis into build/pkgs/SPKG/distros/debian.txt, .../fedora.txt, .../arch.txt for the following purposes:

• sage -info SPKG prints out this information.

• Provide a tox.ini that generates and runs Dockerfiles that test the installation on various systems. Example (running 3 builds in parallel):

     $ tox -p auto -e archlinux-latest,ubuntu-focal-minimal,debian-buster-maximal
  ⠸
  

Incidental change on this ticket:

• Mark gfortran as a type=standard package. It is a prereq of standard package numpy. Its status as a type=optional package predates the clarifications brought by the development of the spkg-configure.m4 mechanism (Meta-ticket: spkg-configure: Try to use as many system packages as possible #27330).

---

Possible follow-up and related tickets:

• Add GitHub Actions workflow for testing the build on various Linux distributions via docker; macOS with homebrew; and Windows (cygwin) #29087 - Add a GitHub workflow that runs this automatically, with many parallel jobs.
• Also the apt-cyg command lines at https://trac.sagemath.org/wiki/Cygwin64Port could be generated in the same way.
• ./bootstrap: Format build/pkgs/SPKG/distros/ information to produce the apt-get/yum command lines shown in the installation manual #26964: Aggregate and format it (during ./bootstrap) to produce the command lines shown in the manual. This ticket already prepares it by moving these command lines into separate .txt files.
• sage_bootstrap: Add command "sage -package list --output={install-requires,requirements,pipfile,debian,....}" #29041: at ./bootstrap time, generate src/requirements.txt, src/constraints.txt, src/setup.cfg [install_requires] from build/pkgs
• Add SAGE_ROOT/environment.yml for "conda env create -f". #28745: Add SAGE_ROOT/environment.yml for conda env create -f.
• Add to tox.ini a conda run (either with a fresh environment or fresh conda install) without docker - to test with macOS conda
• Add to tox.ini a homebrew run (with a fresh install not in /usr/local)

Resources:

• https://repology.org/

CC: @dimpase @embray @antonio-rojas @isuruf @timokau

Component: build

Author: Matthias Koeppe

Branch: 23c6334

Reviewer: Dima Pasechnik

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

[mkoeppe]

Branch: u/mkoeppe/installation_manual__generate__apt_get_install__and__yum_install__lines_from_build_pkgs_at___bootstrap_time

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

3a5cfb7

build/pkgs/*/debian.txt: Add optional packages

[sagetrac-git]

Commit: 3a5cfb7

[sagetrac-git]

Changed commit from 3a5cfb7 to 79d912e

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

79d912e

build/pkgs/*/fedora.txt: New, from installation manual 9.0

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

8a739b1

sage -info: Print info on equivalent system packages

[sagetrac-git]

Changed commit from 79d912e to 8a739b1

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

3ef64c4	Document the debian.txt, fedora.txt files.
ebee631	Add build/pkgs/gcc/fedora.txt
221c344	Strip comments from debian.txt, fedora.txt files

[sagetrac-git]

Changed commit from 8a739b1 to 221c344

[mkoeppe]

Description changed:

--- 
+++ 
@@ -6,6 +6,8 @@
 
 We propose to put this information on a per-package basis into `build/pkgs/SPKG/apt`, `.../yum` or similarly named files and to aggregate it during `./bootstrap` to produce the command lines shown in the manual.
 
+In addition, `sage -info SPKG` prints out this information.
+
 (Similar to #29041.)
 
 

[dimpase]

comment:7

how do you generate these per package?

by the way, Arch has namewise
a naming scheme close to Gentoo and Homebrew.

[mkoeppe]

comment:8

Replying to @dimpase:

how do you generate these per package?

I created these files by manual copy-paste from the installation manual.

[sagetrac-git]

Changed commit from 221c344 to ff4a551

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

46957b4	tox.ini: New - test spkg-configure on ubuntu docker images
ce99fad	Merge tag '9.1.beta1' into t/29053/installation_manual__generate__apt_get_install__and__yum_install__lines_from_build_pkgs_at___bootstrap_time
0dd2c03	build/bin/sage-spkg: Reformat the install command to 1 line
b5abc8b	build/bin/sage-spkg: fixup
97b09de	Make gfortran a standard package - it is a prereq of standard package numpy
ff4a551	Fix typo

[mkoeppe]

Description changed:

--- 
+++ 
@@ -4,7 +4,9 @@
 Several packages are missing, see comments in
 https://github.com/sagemath/sage-prod/files/10659286/Dockerfile-ubuntu-minimal.gz
 
-We propose to put this information on a per-package basis into `build/pkgs/SPKG/apt`, `.../yum` or similarly named files and to aggregate it during `./bootstrap` to produce the command lines shown in the manual.
+We propose to put this information on a per-package basis into `build/pkgs/SPKG/apt`, `.../yum` or similarly named files for the following purposes:
+- Provide a `tox.ini` that generates and runs `Dockerfile`s that test the installation on various systems
+- Aggregate and format it (during `./bootstrap`) to produce the command lines shown in the manual.
 
 In addition, `sage -info SPKG` prints out this information.