Open
Description
Currently ignoring a specific path with patterns (like this) either thorugh the project settings or the a scancode configuration file does not remove these resources from the package assembly, this is beacuse:
- ignoring the resources by path still creates and stores the resources in the directory, it just updates it's status to
IGNORED_PATTERN. I.e. it does not delete the resources from the database - Other subsequent functions/pipes are expected to ignore these files by using this assigned status.
- If package assembly starts from a resource (having some package metadata detected) which is not ignored, then we walk the codebase from this resource to assign codebase resources to this package. This operation does not currently honour the ignored status as these functions are implemented for each ecosystem in scancode-toolkit.