Add support for cargo binstall?

[marxin]

Cargo Binary Install is pretty popular mechanism when it comes to installation of Rust binary tools. Apparently, it's something that communicates with crates.io, but I haven't read the documentation yet.

Once we've included cargo-dist, I thought it would be worth supporting as well. What others think about it?

[mati865]

Wild would have to be published on crates.io first.

[marxin]

@davidlattimore Can you consider publishing the crate to crates.io?

[davidlattimore]

Sure, I guess we can do that. First, we'll need to settle on some package names. For the linker itself, wild-linker would be an obvious choice. I'm wondering if we should rename wild_lib to wild-lib, unless someone else has any better names.

Then there's linker-diff, linker-layout, linker-trace and linker-utils. I guess they're OK, but also open to other suggestions.

[marxin]

Sure, I guess we can do that. First, we'll need to settle on some package names. For the linker itself, wild-linker would be an obvious choice. I'm wondering if we should rename wild_lib to wild-lib, unless someone else has any better names.

I support that and it seems natural to me to have the same name conventions (by using a dash instead of an underscore).

About the other tools: are you planning to make them available as crates on crates.io?

[davidlattimore]

By tools, you mean linker-diff? It's a dev-dependency of wild. I'm not 100% sure, but I think crates.io won't let you publish a crate if its dev dependencies aren't published.

[davidlattimore]

Or do you do mean the non-binary crates like linker-layout? Those we'd definitely have to publish, since they're not even dev-dependencies. Open to rename suggestions though if we think the current names are too generic.

[marxin]

Ah, ok, makes sense one needs to publish all dependencies, otherwise one can't build it properly :)
I'm fine with the currently used names.

[heavyrain266]

I'm wondering if we should rename wild_lib to wild-lib, unless someone else has any better names.

I suggest libwild, Pijul went with libpijul, and I plan to release libjinx. Users can do global alias using:

pub(crate) use libwild as wild

[davidlattimore]

I suggest libwild, Pijul went with libpijul, and I plan to release libjinx.

That seems reasonable to me. I'll probably go with that.