-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
docs(contrib): Describe how to add a new package #12878
Conversation
@Muscraft is considering adding a crate and we felt it was best to not just answer the question of how to do so but to document it!
r? @weihanglo (rustbot has picked a reviewer for you, use r? to override) |
- Add it to `.cargo/config.toml`s `[alias]` table | ||
- Mark `package.publish = false` | ||
|
||
If published, add the package to `publish.py`, in dependency order |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's unclear whether a package is required to add to the list. Can we expand this a bit? Something like
If published, add the package to `publish.py`, in dependency order | |
If published, add the package to the [`TO_PUBLISH` list in `publish.py`](https://github.com/rust-lang/cargo/blob/9bf67a1026c023e2789e867d8b88dc6fc181f357/publish.py#L18-L28), in dependency order. | |
Packages in `TO_PUBLISH` will be published automatically along with each new releases of Rust. | |
Note that every package used by `cargo` the library is required to be available on crates.io, but not necessary to be in the `TO_PUBLISH` list. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was wanting to hold off on getting into that level of detail to be more resilient against change. I have updated it. Is the new version sufficient?
ea592ba
to
9a36c04
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am pretty okay with this doc update 👍🏾.
Thank you.
@bors r+ |
☀️ Test successful - checks-actions |
Update cargo 8 commits in df3509237935f9418351b77803df7bc05c009b3d..708383d620e183a9ece69b8fe930c411d83dee27 2023-10-24 23:09:01 +0000 to 2023-10-27 21:09:26 +0000 - feat(doc): Print the generated docs links (rust-lang/cargo#12859) - feat(toml): Allow version-less manifests (rust-lang/cargo#12786) - Remove outdated option to `-Zcheck-cfg` warnings (rust-lang/cargo#12884) - Remove duplicate binaries during install (rust-lang/cargo#12868) - refactor(shell): Write at once rather than in fragments (rust-lang/cargo#12880) - docs(ref): Link to docs.rs metadata table (rust-lang/cargo#12879) - docs(contrib): Describe how to add a new package (rust-lang/cargo#12878) - move up looking at index summary enum (rust-lang/cargo#12749) r? ghost
@Muscraft is considering adding a crate and we felt it was best to not just answer the question of how to do so but to document it!