Misleading documentation for CIBW_BEFORE_ALL

[doronz88]

Description

I'm trying to use cibuildwheel locally to test stuff before using the GitHub actions.
I an installation prequisite of libssl-dev and followed the guidelines from:
https://cibuildwheel.readthedocs.io/en/stable/setup/

However, when I try exporting CIBW_BEFORE_ALL to use apt just as the example suggests, I'm getting an error that no apt binary exists.

Build log

No response

CI config

No response

[joerick]

Which build fails? Link a build log. What's your exact config? etc.

[doronz88]

Just discovered the real culprit - the documentation!
I got by the solution suggested in #1034 - I had to try and install using all package manager variations.
The documentation should be updated to reflect this is necessary.

[Czaki]

The source of the problem is that not all docker images are debian based.
I think that this artifact from the time when manylinux temporarily switched to debian based. But currently, all things are almalinux (RedHat) and Alipne (muslinux) which both have their own installers and package names.

[doronz88]

I get that, but I believe the documentation should state that it is built on several linux distros with different package managers. Usually, I expect documentation examples to work as-is.

[joerick]

ah, yeah that isn't a good snippet to include so early in the docs, and it is outdated given that the default image is now almalinux-based.

The point of this snippet is to show how to pass options to cibuildwheel. So we should change it to something less platform-dependent. CIBW_BUILD_FRONTEND=build could be a non-controversial replacement that works everywhere.

PR would be welcome for this!

[doronz88]

Updated my PR for that #1686