-
Notifications
You must be signed in to change notification settings - Fork 46
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
Have cargo vet prune
remove old redundant policy fields
#490
Comments
I'm not sure how easy it would be to implement in practice, because this surfaces as an error, whereas We could of course just make the tool automatically remove the irrelevant entries, but we went with an explicit error so that (1) it would be less mysterious why a policy entry was disappearing, and (2) users would be less likely to inadvertently drop an important policy when a crate was renamed or something. |
The On that note, if you weren't aware of that subcommand, I believe you should be able to run it rather than removing the entries manually as well. |
does |
I'm not sure. @mystor ? |
Apparently it does not, though there is a comment in the logic considering that behaviour dating back to #368 though. Lines 1918 to 1919 in 3c3f1e0
At one point I think I had considered pruning completely empty |
If you have removed a dependency that you had a
[policy.crate-name]
for in yourconfig.toml
you get the following nice and clear warning:though instead of having to remove that manually in your config file, is this something
cargo prune
could do for you to streamline things?The text was updated successfully, but these errors were encountered: