manylinux packages for Python

[FRidh]

This adds three lists with manylinux dependencies as well as three
packages that include all the manylinux dependencies.

Motivation for this change

Thanks to @thomasjm for their work in #55812.

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

Notify maintainers

cc @jonringer @adisbladis @thomasjm

[jonringer]

I think you need to also edit the interpreters so that they say they are "manylinux" compliant

  echo "manylinux1_compatible=True" >> $out/lib/${libPrefix}/_manylinux.py

[FRidh]

yes, that's a separate step. I'm still thinking about the interface.

[jonringer]

should we mark this as WIP then?

[FRidh]

No, I make that change separate as it would be a mass-rebuild. This is usable without anyway.

[jonringer]

Yea, that's fair

[jonringer]

This is kind of confusing as a top-level attribute (as it's python specific, but seems like it could be something broader), I think the manylinux* builders should live alongside buildPythonPackages under pythonX.pkgs

I'm also in favor of them being renamed from manylinuxXXXXPackage to buildManylinuxXXXXPackage

[FRidh]

This is kind of confusing as a top-level attribute (as it's python specific, but seems like it could be something broader)

These are not Python libraries, but just lists of derivations. They are used with Python packages but are not Python-version specific. Having some kind of indicator that they are related to Python is not be a bad idea.

I'm also in favor of them being renamed from manylinuxXXXXPackage to buildManylinuxXXXXPackage

They are not build functions either. The lists are just that, lists, and the other ones are derivations but are not meant to be used; you do not want to patchelf libs via the symlink tree because you would retain too many dependencies that way.

Ideally every package set contains only derivations, not functions or anything else. We're far from there but its important to consider.

[jonringer]

hmmm, I abandon my renaming stance, but still think it should be moved to python.manylinuxPackages, or python.pkgs.manylinuxPackages

[adisbladis]

@FRidh I have renamed manylinuxPackages to pythonManylinuxPackages (as suggested on IRC) and rebased.

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/mach-nix-create-python-environments-quick-and-easy/6858/17