Provide more pre-built binaries

[NobodyXu]

It would be great to provide:

• aarch64-apple-darwin builds
• universal-apple-darwin builds
• provide *-musl builds for all *-gnu builds
• provide a new type of builds which uses zlib-ng for max perf and linked with it statically, uses rustls to avoid external openssl dep.

Originally posted by @NobodyXu in #1239 (comment)

[mattyclarkson]

aarch64-linux-{musl,gnu} builds, if possible.

[EliahKagan]

And no amd64 linux bin?

Some such builds are published, so I'm not sure what you're referring to, but I can think of three things.

They are labeled x86_64

In Rust target names, AMD64 targets are labeled x86_64. So the archives built by release.yml, and attached to GitHub releases such as v0.44.0, include such builds, but searching for "amd64" does not find them. For example, that most recent gitoxide release has:

• gitoxide-max-pure-v0.44.0-x86_64-unknown-linux-gnu.tar.gz
• gitoxide-max-pure-v0.44.0-x86_64-unknown-linux-musl.tar.gz

For now, they are max-pure only

Those are max-pure builds. It may be that you are looking for builds with other (combinations of) features, such as max, small, and lean, as are built and published for various other operating systems.

Unfortunately, we have not been publishing such other Linux builds, due to difficulties producing them in a correct and portable way. I anticipate that this problem can eventually be fixed. One of the factors is, or at least has been, that we are using cross for the Linux builds, and the cross Docker images don't have OpenSSL. But I think there may be other hurdles to overcome, for the *-gnu targets, because different operating systems have different library versions, including of glibc itself, and non-"pure" *-gnu builds make greater use of dynamic linking.

I think we may have a separate issue or something for this. But I'm not sure if we do. It's touched on in #1498 (reply in thread), but it's broader than that. In any case, this is sort of referenced here. From the issue description above:

• provide a new type of builds which uses zlib-ng for max perf and linked with it statically, uses rustls to avoid external openssl dep.

But I think that specific goal may need to be updated in view of #1963.

Why x86_64 wasn't mentioned here

If you're just asking why Linux amd64/x86_64 hadn't been mentioned in this issue, even though some builds for it that we would ideally produce are not (yet?) being produced, I think the reason is that the limitation isn't specific to that architecture. Other Linux builds beyond max-pure are also, and for the same reasons, not currently published.

[vitaly-zdanevich]

Thanks, sad that we cannot pull :(

[Byron]

With pull, Are you referring to functionality of the gix binary? If so, then it's true that this isn't implemented and if it ever will be, it would still need gix reset to be made available as well. That is definitely on the roadmap, even though for now I had no plans to make a git pull equivalent.

[vitaly-zdanevich]

For guys from a search looking for portable git - I found https://pkgs.pkgforge.dev/repo/pkgcache/x86_64-linux/git/appimage/ppkg/stable/git