Allow specifying target semver ranges about cargo-update

[nabijaczleweli]

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 with cargo-install – I harbour a deep-seated hatred for cargo's CLIs (unintuitive at best, bloody useless at worst), so that is not and has never been a priority (also consider how cargo-update solves a completely different problem domain).

[CAD97]

Makes sense. I just sort of spitballed a rough design expecting further refinement.

I'm glad to see this is available now!

[nabijaczleweli]

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

[CAD97]

I'll get a chance to try it out this evening, right now I'm limited to just looking at the patch on my phone.

The one edge case I'm worried about and tried to address in my sketch is specifying a version requirement and multiple crates. So maybe -a --version ^1.0 for example. Version is a by-crate status, not a general setting.

I can't tell exactly how master behaves without trying it out, so I will this evening. I've now circled around and repeated myself so I need to go do what I'm supposed to be doing :P

[nabijaczleweli]

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

[CAD97]

I'm so sorry about the delay, obviously a series of other things appeared and delayed me.

I actually can't install cargo-update right now because something about my Visual Studio setup is messed up, though, and libssh-sys won't build because of a CMake error: could not find any instance of Visual Studio.

[nabijaczleweli]

(Temporarily marking as external 'till that VS issue is resolved)

[nabijaczleweli]

@CAD97 bump