meta: Explicitly include items in packaged crate#5312
Conversation
|
Does it maybe make sense to switch from |
There was a problem hiding this comment.
I think that's the better path. Would you be able to change the exclude to include? And cover at least:
- src
- tests
- examples (doesn't exist now but could in the future. Not sure if it will reject it)
- build.rs
- CHANGELOG*
- LICENSE*
- README*
(if you could post a diff of cargo package --list, that would be helpful too. Otherwise I can get it)
|
Reminder, once the PR becomes ready for a review, use |
Added in 27a38e3 causes `cargo-deny` warnings due to the inclusion of an executable Python script.
a85e8f8 to
972f696
Compare
Yeah I think that makes more sense. I would assume it's easier to notice (and yank) if a
The non-existent 2,6d1
< .editorconfig
< .git-blame-ignore-revs
< .gitignore
< .release-plz.toml
< .rustfmt.toml
8d2
< CONTRIBUTING.md
16,17d9
< etc/libc-util.py
< rust-bors.tomlI think all of those make sense to exclude, but happy to amend! |
|
@rustbot ready |
/etc from Package
Description
Exclude
/etcfolder fromcargo packageby explicitly listing items to include. Currently published version oflibcincludes/etc/libc-util.pywhichcargo-denypicks up as an executable. Added in 27a38e3Checklist
Relevant tests inN/Alibc-test/semverhave been updatedCommit messages permalink to headers for added or changed APIN/APlaceholder or unstable values likeN/A*LASTor*MAXhave the standard doc commentcargo test -p libc-test --target mytarget);cargo packageand inspecting that the Python script is excluded.@rustbot label +stable-nominated