Aria Desires

The current support for binaries with requires features is for you to use `features`/`all-features`/`default-features` in `workspace.metadata.dist`/`package.metadata.dist` (same syntax as cargo dependencies): https://opensource.axo.dev/cargo-dist/book/reference/config.html#features

Also to be clear here, `required-features` is a Cargo feature that can only *disable* a binary being built. It sadly does not tell Cargo "hey if I try to build...

(We *could* read required-features config and flip on features by default but I'm a bit skittish about confusing things happening if we do that automagically.)

> Yes precisely, this is a mechanism to disable including a binary. If the binary feature is not part of the default features, I would expect cargo-dist to not try...

possible dupe of #21

(making this a more specific task)

With #243 done this is the next logical step for integrity/checksum/signing stuff but i'm definitely in "i have no idea what i'm doing" territory with sigstore

Yep!

We have now forked/vendored binary-install, and so we have the ability to fix this. The JS code that needs to change is here: https://github.com/axodotdev/cargo-dist/blob/e64776d69f7dda13f4e7dcb99d2714efc187740a/cargo-dist/templates/installer/npm/binary-install.js#L83-L91 Given the above researach I think...

Let's assume we're renaming to "dist": * add a bin-alias so that cargo-dist.exe and dist.exe both exist * teach the clap CLI to not require the "dist" dummy arg that...