Follow license reference to another file - #2616
Conversation
Signed-off-by: akugarg <akanksha.garg2k@gmail.com>
Signed-off-by: akugarg <akanksha.garg2k@gmail.com>
|
Hey! @AyanSinhaMahapatra How we will go about adding same logic for packagecode like we discussed yesterday? |
|
Also, for packagedcode, say for npm, see here. We have a function converting a list of license declarations to a license-expression. It would have been ideal if we return some form of License Detections here instead of just the expressions (which is WIP), but in a short term we could check first for these kind of license references to file (and report only the license conclusion without the unknown). |
Signed-off-by: akugarg <akanksha.garg2k@gmail.com>
29ddb8a to
4aab0aa
Compare
2ba8f14 to
4559aab
Compare
3200da4 to
d4f1436
Compare
|
@AyanSinhaMahapatra @pombredanne Please have a look! |
pombredanne
left a comment
There was a problem hiding this comment.
Thanks! beside the review comments, I would also like to see some unit tests for find_reference_licenses
d478c25 to
10385da
Compare
10385da to
27146ae
Compare
Signed-off-by: akugarg <akanksha.garg2k@gmail.com>
27146ae to
a84b1ed
Compare
pombredanne
left a comment
There was a problem hiding this comment.
I have a few final review items for you. Thanks!
Signed-off-by: akugarg <akanksha.garg2k@gmail.com>
b8544b1 to
466e375
Compare
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Only follow license references match an exact filename In #2616 we introduced matching path of referenced_filenames based on matching filename or path suffix. This removes path suffix matching which is problematic. Before this we were using .endswith(path) and this led to weird and incorrect license dereferences Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Signed-off-by: akugarg akanksha.garg2k@gmail.com
Fixes #1364
Tasks
Run tests locally to check for errors.