-
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
Publish Cargo Manual on the bookshelf #44910
Comments
I took a stab at this today, but didn't get it working; our book build system generally expects for the book to be in the |
Yeah, I ended up in a similar situation and started touching many functions to make them flexible enough to handle this case. If you think it's better to make changes on the |
Let me give it another go before we try that; I'm not totally sure that helps a ton. That is, as far as I can tell, it'd have to literally be in |
I did it! PR incoming. |
Awesome, @steveklabnik! I created a follow up task on Cargo to finish the migration: rust-lang/cargo#4694 |
Fixes rust-lang#44910 Fixes rust-lang#39588 See both of those bugs for more details.
Background
In rust-lang/cargo#4040, we re-organized Cargo documentations into one single in-repo mdBook, called "Cargo Manual". The preview is available on http://doc.crates.io/book/
Now
The last step is to publish the book on https://doc.rust-lang.org/cargo/, which requires work in this repo (
rust
).Follow-up
After this, we should create a new tracker issue in Cargo to deprecate
doc.crates.io
and redirect them todoc.rust-lang.org
. [rust-lang/cargo#4694]Part of #39588
The text was updated successfully, but these errors were encountered: