Currently, cargo-bundle-licenses determines the packages to bundle licenses for by evaluating the dependency tree for the top-level project with its default features selected. However, it may happen that a developer wants to distribute binaries built with a non-default feature selection (instead of or in addition to binaries with default features), and so they would need a license bundle that reflects the dependencies added & removed by the change in features, but cargo-bundle-licenses does not provide that.
I therefore request the ability to specify a set of features to apply when determining a project's dependencies.
Currently,
cargo-bundle-licensesdetermines the packages to bundle licenses for by evaluating the dependency tree for the top-level project with its default features selected. However, it may happen that a developer wants to distribute binaries built with a non-default feature selection (instead of or in addition to binaries with default features), and so they would need a license bundle that reflects the dependencies added & removed by the change in features, butcargo-bundle-licensesdoes not provide that.I therefore request the ability to specify a set of features to apply when determining a project's dependencies.