Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fork the pypa/manylinux repo and build slim images #1

Open
bastimeyer opened this issue Jan 29, 2025 · 0 comments
Open

Fork the pypa/manylinux repo and build slim images #1

bastimeyer opened this issue Jan 29, 2025 · 0 comments

Comments

@bastimeyer
Copy link
Member

With the availability of native aarch64 CI runners on GH, forking pypa/manylinux and slimming down the builds is now an option without having to fall back to another free CI provider. GH's container registry can easily be used while everything's run here.

The manylinux images include Python builds of all supported Python versions, which bloats them up quite heavily. This is the main motivation for forking the build config.

In addition to that, OpenSSL is currently not built for manylinux_2_28 and the 1.1.1k builds from AlmaLinux 8 are included instead, as they pass py310+'s requirements.

Forking however means that upstream will need to be merged back regularly, because I won't maintain this myself. Merge conflicts shouldn't be a problem though unless we apply more modifications.

I'm not sure yet how I'm going to handle this repo if manylinux will be forked. Maybe it'll be replaced and its build config will be applied to the fork, or it'll build off of images of the fork (which would unnecessarily duplicate lots of data).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant