Take build dependencies into account during license checks
The comment says that build dependencies shouldn't matter unless they do some kind of codegen. It is safer to always check it though.
This commit is contained in:
parent
2fa18b8864
commit
5db01aae99
1 changed files with 1 additions and 10 deletions
|
|
@ -460,16 +460,7 @@ fn normal_deps_of_r<'a>(
|
|||
.iter()
|
||||
.find(|n| &n.id == pkg_id)
|
||||
.unwrap_or_else(|| panic!("could not find `{}` in resolve", pkg_id));
|
||||
// Don't care about dev-dependencies.
|
||||
// Build dependencies *shouldn't* matter unless they do some kind of
|
||||
// codegen. For now we'll assume they don't.
|
||||
let deps = node.deps.iter().filter(|node_dep| {
|
||||
node_dep
|
||||
.dep_kinds
|
||||
.iter()
|
||||
.any(|kind_info| kind_info.kind == cargo_metadata::DependencyKind::Normal)
|
||||
});
|
||||
for dep in deps {
|
||||
for dep in &node.deps {
|
||||
normal_deps_of_r(resolve, &dep.pkg, result);
|
||||
}
|
||||
}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue