-
Notifications
You must be signed in to change notification settings - Fork 109
Map archives when their extracted directory mapped/processed #827
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
Comments
@pombredanne Some notes looking at the data on a ScanCode.io instance:
Resources with the following extensions are flagged as
Keeping the scripts to revisit this later:
|
Reference: #827 Signed-off-by: Ayan Sinha Mahapatra <[email protected]>
* Assign status to processed archives Reference: #827 Signed-off-by: Ayan Sinha Mahapatra <[email protected]> * Add test to check archives are assigned status Signed-off-by: Ayan Sinha Mahapatra <[email protected]> * Fix test failures Signed-off-by: Ayan Sinha Mahapatra <[email protected]> * Address review comments and add CHANGELOG entry Signed-off-by: Ayan Sinha Mahapatra <[email protected]> --------- Signed-off-by: Ayan Sinha Mahapatra <[email protected]>
See also : @JonoYang wrote:
It would help to be able to navigate from a resource to its extracted directory at least in the UI (and possibly also in the DB and API) |
In a deploy_to_devel pipeline, when I have an archive like "foo.zip", there will be a directory "foo.zip.extract" with the extracted content.
If "foo.zip" is matched to the purlDB then "foo.zip.extract" should be treated as matched too. This is already the case.
Otherwise, if not matched to the devel side and not matched to the purldb, "foo.zip" should be assigned an "extracted" status right at the end of the step that is matching archives to the purldb and this archive should not be further processed. This works because we have its extracted content that is processed otherwise.
We need to validate that:
The text was updated successfully, but these errors were encountered: