наб

Sure, open a PR, though I'm not sure what you'll gain from JSON specifically that you can't get out of the current output at present

I don't feel like potentially reimplementing Cargo's package resolution and I'm not quite sure that this is entirely in scope, so send a patch if you want this.

## The argument list Okay, let's go top-down. > cargo-update needs to do this differently It's not *just* `cargo-update`, it's every crate produced by me. Why? Stay tuned. > The...

Sorry for the delay, but the actual command executed by `cargo-update` is `cargo install -f --git https://github.com/redox-os/ion ion-shell` (note the `ion-shell` package spec), so if you could re-try with that...

Despite `ion-shell` not building on my machine I just faked it, and: ``` $ cat .cargo\.crates.toml [v1] "cargo-update 0.8.1 (registry+https://github.com/rust-lang/crates.io-index)" = ["cargo-install-update-config.exe", "cargo-install-update.exe"] "ion-shell 0.5.3 (git+https://github.com/redox-os/ion#f81f0ddf11b5258a52b374dc87f14f8a3857816e)" = ["ion-shell.exe"] $ cargo...

So, `external` and an issue there, right?

hmm I'm guessing this is resolved, then?

Check latest `master`. As for the design-thingy – full of specialcases and completely ignores the current infrastructure for setting per-package config, so it obv didn't go in. As for compatibility...

Right, so does it behave as you'd expect? If so, I'm gonna release it.

So, "this evening" was a good four months ago – how was it?