Selection of runner for Github CI

[MrHedmad]

Selection of runner for Github CI

[MrHedmad]

I've added the rustls-tls feature to reqwest and the binary size is identical. Still need to try it out but I guess that solves my issue! I'll leave closing to you; maybe you wish to still include the option to change runners.

Thank you for the ultra-fast reply!

[Gankra]

So we do hardcode to the oldest possible runner we can find specifically to link against the oldest possible libraries. In particular we want to link against the oldest possible glibc, so that the linux-gnu binaries are as portable as possible (for instance, iirc github codespaces defaults to running on 20.04, so binaries built on 22.04 fail to run there 😭).

Also just checking: you do for reals want to be linking openssl, yeah? Most rust projects try to avoid this, opting to statically link rust-tls: https://github.com/axodotdev/gazenot/blob/ef900eca9c9c8309290b303faebae85cafebf9c5/Cargo.toml#L31-L35

[Gankra]

(I'm not opposed to having settings to bump up the runners, just first checking that it actually solves your problem)

[MrHedmad]

I'm a Rust beginner so I'm still not familiar with all of this linking issues. But if I can avoid relying on opensll of course it would be best. The only issues I got when including openssl (see here) is that the binary size baloons. But I had no idea that reqwest can use something else entirely, as you show. I'll try it and check binary sizes. But I think that probably will fix the issue.

Still, maybe an obscure option somewhere to set the runners might still be useful to someone, at some point!