Félix Saparelli
Félix Saparelli
Right, well, that's not a great experience. I wonder if we could rig it such that it defaults to two binaries, but produces a multicall given a feature. That way...
We still want to cooperate with the standard files for global installs. Not entirely sure what to do with them, though, regarding file locking and proper handling and such. I...
The idea for meta files support, separate from this issue, was for cargo-update to be modified to pull from cargo-binstall when available, originally.
Hmm, toml_edit taking a while is annoying, as I wanted to use that for our own manifest, at least the human-writable bit
Hmm, we could compromise by writing only the simpler toml/v1 file which doesn't have any of these things, so that cargo-update can be used to update via cargo-install if the...
So, the reason I had both `tool` and `package` sections in the OP is because there's two concepts of "source": the metadata source, and where the particular file came from...
well, the original thing is to have both the manifest and the lockfile in tandem, modelled like Cargo. Cargo.lock has a fully resolved tree, so if you dev on linux...
I also kinda want to avoid the proliferation of many different files that we write to. ...or maybe we say, let's go and write as many files as we want...
That's very cool! One thing I will point out, we'd want to gate this behind a flag, so that `cargo install cargo-binstall` still works out of the box on stable
what would be excellent is if we could manage to make a multi architecture APE like the original article hints at. x64 and arm7 and arm64