possible wrong rules triggering

[armijnhemel]

Description

In the BusyBox project I can see the phrase

and put under GPLv2 license.

which can be found at https://github.com/mirror/busybox/blob/master/networking/tls_aes.c#L39

This triggers https://github.com/aboutcode-org/scancode-toolkit/blob/develop/src/licensedcode/data/rules/gpl-2.0_818.RULE

but it doesn't report https://github.com/aboutcode-org/scancode-toolkit/blob/develop/src/licensedcode/data/rules/gpl-2.0_493.RULE which would also be valid. This rule catches a little bit less, but also a little bit more. My question to @pombredanne and @AyanSinhaMahapatra is what the best course of action would be:

1. ignore and just go with the 818 rule
2. ignore and go with the 493 rule
3. create a new rule that combines the two rules

How To Reproduce

Tell us how to reproduce the issue.

System configuration

For bug reports, it really helps us to know:

• What OS are you running on? (Windows/MacOS/Linux)
• What version of scancode-toolkit was used to generate the scan file?
• What installation method was used to install/run scancode? (pip/source download/other)