auditwheel choose higher priority tag when possible

[messense]

Example:

🍹 Building a mixed python/rust project
🔗 Found pyo3 bindings
🐍 Found CPython 3.9 at /opt/python/cp39-cp39/bin/python
   Compiling pyo3 v0.13.2
   Compiling pyo3-mixed v2.1.1 (/io/test-crates/pyo3-mixed)
    Finished dev [unoptimized + debuginfo] target(s) in 6.46s
📦 Built wheel for CPython 3.9 to dist/pyo3_mixed-2.1.1-cp39-cp39-manylinux2010_x86_64.whl
📦 Wheel is eligible for a higher priority tag. You requested manylinux2010 but I have found this wheel is eligible for manylinux1
📦 Fixed-up wheel written to dist/pyo3_mixed-2.1.1-cp39-cp39-manylinux1_x86_64.whl

[konstin]

This is great 👍

[konstin]

I think the ideal solution would be having three categories:

• auto (default): Goes from the highest to the lowest priority, tags the first one that matches. If nothing matches, uses manylinux
• 2010/2014/2_24/etc.: Tag exactly this version. maturin should tell users about a higher priority tag, but tag the one requested.
• off: Tags linux

There might be a case for a fourth option, manylinux, which tags the highest manylinux possible and fails if only linux would match.

This PR is already a huge improvement as-is, so I'm happy with merging this now and figuring out the specifics of the cli arguments later

[messense]

This PR is already a huge improvement as-is, so I'm happy with merging this now and figuring out the specifics of the cli arguments later

Sure, let's do that later in #448

[messense]

auto (default): Goes from the highest to the lowest priority, tags the first one that matches. If nothing matches, uses manylinux

Do you mean If nothing matches, uses linux?

[konstin]

Oops, yes that should have been linux