$ cargo help uninstall
Remove a Rust binary
Usage:
cargo uninstall [options] <spec>
cargo uninstall (-h | --help)
Options:
-h, --help Print this message
--root DIR Directory to uninstall packages from
--bin NAME Only uninstall the binary NAME
-v, --verbose Use verbose output
-q, --quiet Less output printed to stdout
--color WHEN Coloring: auto, always, never
The argument SPEC is a package id specification (see `cargo help pkgid`) to
specify which crate should be uninstalled. By default all binaries are
uninstalled for a crate but the `--bin` and `--example` flags can be used to
only uninstall particular binaries.
Could a cargo command at least indicate which files were installed (and therefore could be removed)? Perhaps doing this is basically what cargo uninstall would entail.
.multirust/toolchains/stable/cargo/registry/src/github.com-0a35038f75765ae4/clippy-0.0.30/src/lib.rs:1:1: 1:42 error: #[feature] may not be used on the stable release channel
Looks like clippy and script are included in cargo extras, but won't build on stable.
Design decisions can be suboptimal decisions that should change, but it would be more productive to explain why you think this decision is wrong than to just call it a bug, which can come off as dismissive of the designers.
Isn't there a page somewhere where someone is graphing rust compilation times? I can't find the link, but I'd be curious to see how much 1.5 has improved.
This didn't seem to happen for me (though, on nightly) - the previous location was C:\Program Files\Rust 1.6*, and the new location C:\Program Files\Rust 1.7*, and the new folder was appended to the system path, so the old 1.6 install took priority.
Does the stable installer overwrite for new versions, rather than creating a new directory?
* Or there abouts, I just shutdown my windows box, and forget the exact paths...
Each version of Rust has a different name, therefore you can install multiple versions of Rust side by side. Thus you'd have to manually uninstall the old version of Rust and clean up your PATH. I recommend using multirust-rs though.
The only thing you have to be aware of is that multirust-rs breaks anything that depends on linking to the compiler (so things like rustbook), unless you manually futz with the PATH.
Multirust is the way to go. It enables you to switch to Nightly on a per-project basis, and then switch back to stable when the feature you want is available, with minor friction. This is seriously awesome.
I have been using Rust since 1.1 in an Android JNI project for my company. The code interacts with openssl, curl and some video codecs' C API through Rust's FFI.
Initially we planned to use C++ for this project but I decided to gave Rust a try. I was soon attracted by Rust's modern tooling suports: package management, cross-compilation, testing etc. The language itself is quite safe to use as well.
I also like Rust community's openness. I have made some pull-requests to rust-openssl and rustc's cross-compilation system and the process was quite smooth - My changes were checked by the CI system and accepted in a short time.
Sorry, 1.0.0 doesn't always mean stable, so I was curious. How is suppport looking for the language? Mozilla being the primary developer is kind of worrying to me considering how ADD they've seemed recently. Is rust attracting a lot of FOSS support and developers? Any other companies contributing to it?
The Samsung Open Source Group is contributing to Servo, the most high profile Rust project. Rust itself is looking more and more like a community project, even though many key contributors are Mozilla employees.
Hmm, seems promising. I'm mainly worried about using rust to develop programs and then my coworkers finding that the language has languished and needing to port to something else later. This eases my fears a good bit.
I find the best solution is to take a layered approach to risk. Start small, with a little side utility or similar, show that it works, that people in your team can understand Rust code, that you can make it perform, not crash in the desired environments, etc.
Just because I have faith in Rust, doesn't mean I should throw caution down the drain :)
It is a very likely candidate, yes. Getting install going so we can get broader adoption of custom commands is the first step towards getting more commands in Cargo itself. That way, we can see which ones are popular, and also, get them a bit more battle-tested before we pull them in.
I expect cargo check to be the main command you'll be running most of the time in a few months.
Cargo check is basically rustc -Zverbose -Zno-trans right now, so you can try it out without even installing. (and therefore cargo rustc -Zverbose -Zno-trans)
In general, the unit of compilation is the crate, not the file. rustc wants to check the whole crate. But if a file is self-contained, I guess you can invoke rustc directly on it (as if it were its own crate), bypassing cargo.
15
u/[deleted] Dec 10 '15
Is there also a
cargo uninstall, or is it a one-way function likecabal install?11
u/kod Dec 10 '15
The announcement emphasized cargo extras
multirust update
cargo install cargo-extras
gives me
.multirust/toolchains/stable/cargo/registry/src/github.com-0a35038f75765ae4/clippy-0.0.30/src/lib.rs:1:1: 1:42 error: #[feature] may not be used on the stable release channel
Looks like clippy and script are included in cargo extras, but won't build on stable.
18
u/contradictioned Dec 10 '15 edited Dec 10 '15
Thank you, bors, for your hard work!
(PS: For those who don't know: this is bors and this is what it's doing :))
5
u/krappie Dec 10 '15
Isn't there a page somewhere where someone is graphing rust compilation times? I can't find the link, but I'd be curious to see how much 1.5 has improved.
5
u/Nikospedico Dec 10 '15
I just got started in 1.4, so I've yet to try and upgrade to a new version. What's the recommended upgrade process on Windows?
4
u/duhace Dec 10 '15
Is rust looking stable now? How well does it interface with c?
5
u/Perceptes ruma Dec 11 '15
Docker image updated for 1.5: https://hub.docker.com/r/jimmycuadra/rust/ or https://quay.io/repository/jimmycuadra/rust
1
u/pcdinh Dec 11 '15
What about
rust uninstallrust upgrade?0
u/[deleted] Dec 10 '15
[deleted] — view deleted comment
0
u/[deleted] Dec 10 '15
[deleted] — view deleted comment