Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please publish rustup to crates.io #835

Open
joshtriplett opened this Issue Nov 25, 2016 · 7 comments

Comments

5 participants
@joshtriplett
Copy link
Member

joshtriplett commented Nov 25, 2016

Please consider publishing rustup releases as a crate on crates.io. That would make it easier to package rustup releases for Linux distributions, or to install rustup via "cargo install rustup" if you have Rust and Cargo already installed via your distribution. (There's a lot of value in having rustup packages even in a distribution that already has Rust packages, such as to install nightly or to install a cross-toolchain.)

@brson

This comment has been minimized.

Copy link
Contributor

brson commented Dec 16, 2016

I'm happy to make publishing rustup part of the release process. I think right now the blocker is that there are some non-crates.io deps, particularly in the download crate.

@brson brson added the help wanted label Dec 16, 2016

@brson

This comment has been minimized.

Copy link
Contributor

brson commented Dec 16, 2016

Next step is to get rid of git deps in rustup.

The rustup library may need to be broken into another crate and all the libs version numbers dropped to < 1.0.

@xen0n

This comment has been minimized.

Copy link
Contributor

xen0n commented Dec 16, 2016

FWIW rustfmt is properly packaged without crate separation by putting CLI drivers in the seemingly implicit path src/bin. Maybe we could do the same by refactoring main() out of rustup-cli after re-organizing everything?

What's most important though, is defining how rustup as a library should be invoked. Maybe the testsuite way is worth considering?

@xen0n

This comment has been minimized.

Copy link
Contributor

xen0n commented Dec 16, 2016

Also the peculiar way rustup currently installs itself, hard-linking, may be difficult to implement for Cargo installs, but I haven't looked into it. The library interface thing is actually way less relevant if all we want is just enabling cargo install rustup.

@brson

This comment has been minimized.

Copy link
Contributor

brson commented Jan 6, 2017

Oh I misunderstood this issue. I was not considering publication of the rustup binary, only the libs. I don't know how publishing rustup binaries via cargo would work offhand.

@joshtriplett

This comment has been minimized.

Copy link
Member Author

joshtriplett commented Jan 7, 2017

@brson I'd like to have the rustup binary crate available via cargo, allowing cargo install --root=/some/path rustup to install rustup to /some/path/bin/rustup. That seems similar to installing a binary from any other crate via cargo install.

This would require rustup to have all its dependencies on crates.io as well.

@Diggsey Diggsey added this to Features (inclination: accept) in Issue Categorisation May 3, 2017

@infinity0

This comment has been minimized.

Copy link

infinity0 commented Nov 2, 2018

Hi I'd like to bump this. Some people would like to be able to install rustup in Debian so they can easily get access to rust nightly, which we don't package in Debian.

This would allow people to run aptitude install rustup instead of curl blah://blah/sh | sh.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.