-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Rustpkg "ready for use" metabug #5677
Comments
ghost
assigned catamorphism
Apr 2, 2013
This was referenced Apr 2, 2013
This was referenced May 9, 2013
Closed
This was referenced Jun 19, 2013
Not a release blocker, de-milestoning Nominating for milestone 3, feature-complete |
accepted for feature-complete milestone |
closing as rustpkg is gone, and these linked bugs are tightly tailored to that particular artifact, not general packaging. |
tesuji
pushed a commit
to tesuji/rustc
that referenced
this issue
Jun 4, 2020
Fix false negative of `checked_conversion` lint Closes rust-lang#5675 changelog: none
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rustpkg shipped in 0.6 essentially "not ready for use". It is not operating the way we want it to, long term, and we want to get it fixed up and usable by the community early in the 0.7 cycle. This is a tracking bug for major issues associated with its behavior.
Cross these issues off as you complete 'em
use of pkgids (Rustpkg should operate on a URL-like pkgid #5679)crate inference (Rustpkg should infer crates to build #5680)extern mod
for dependencies (Rustpkg should extract dependencies fromextern mod
statements. #5681)RUST_PATH
(Rustpkg and rustc should use RUST_PATH env var to locate packages #5682)testing (Rustpkg needs to be testable #5683)VCS versions in pkgids and dependencies (Rustpkg should support versions integrated with a VCS #5684)using workcache (rustpkg should use workcache #7075)recursive dependencies (rustpkg test case for recursive dependencies #8524)installing to RUST_PATH (Use RUST_PATH to determine where to install to #7402)package IDs pointing into a subdirectory (Allow package IDs to refer to the middle of a source repository #6408)The text was updated successfully, but these errors were encountered: