Add data/images.yml with info about OS inside

[abitrolly]

There is a missing info about which package manager should be used in which manylinux image. I am not an expert in MkDocs, but I've seen another file here, so if this YAML can be turned into some table in documentation, that would be helpful I guess. Which is missing is to how to search package names in AlmaLinux online. https://repology.org/ works somewhat, but it still not clear where the package sources and issue tracker for requests.

[joerick]

This information could be useful as a Markdown table in the option docs. We probably don't need the YAML file though. Could you reformat the information as a Markdown table and put it in the relevant place in options.md?

[henryiii]

As a markdown table you could also easily add a footnote about manylinux_2_24 being EoL and likely to be discontinued (with a link to pypa/manylinux#1332). Or simply not include it.

FYI, yum still works on RHEL 8, though if it's present, dnf is "dandified yum" and better (and faster from what I can tell). There are small differences for redistributions like Alma; one of the main ones is likely activating EPEL, which had a "centos" in the package name for CentOS. Could be worth a mention too.

We should include musllinux which uses apk. Also apt is the package manager for Debian.

[abitrolly]

I would actually prefer to fetch the YAML from https://github.com/pypa/manylinux#manylinux to extract the relevant info from it, but as it also ships with markdown table, so decided to start from here.

As a proponent of open data and datacentric approach to everything, I don't feel like formatting markdown tables by hand. However, if somebody points me how to render data files with MkDocs, I may be able to contribute the formatter.

[abitrolly]

for redistributions like Alma; one of the main ones is likely activating EPEL

Alma doesn't activate EPEL. I even got downvoted for asking why.

https://www.reddit.com/r/AlmaLinux/comments/vg1kj2/comment/iczn7cw/?utm_source=share&utm_medium=web2x&context=3

[abitrolly]

But manylinux could actually activate EPEL for docker images pypa/manylinux#1338

[henryiii]

What I meant is that activating EPEL is likely different for each RHEL clone. And it's by no means the "correct" thing to do for everyone; you happened to find an EPEL package you needed, so you want to activate it. Often you might not need those packages, and often you might be testing a required procedure and not want things (like EPEL) to be activated. For example, if I grab an image and work out the minimum required set of steps to make a package work, I would not want some steps to be missing on Alma that are required on RHEL or the other clones of it! EPEL has some handy packages, but it's not "required". It's just some extra packages. There are other repos with other extra packages, too.

[abitrolly]

I hope we are still speaking in the context of cibuildwheel users who just need to build a wheel for a new version of Linux without getting into the intricate details of RHEL Alma EPEL relationships (#1157).

[joerick]

I don't feel like formatting markdown tables by hand. However, if somebody points me how to render data files with MkDocs, I may be able to contribute the formatter.

Sounds overengineered to me! This data doesn't change that often, a hard-coded markdown table would be fine.

[joerick]

Feel free to reopen if you want to format as a markdown table. Actually I think it might be more useful in the Tips and Tricks section of the docs, here.