Any ETA?I would suggest holding off on that, as we are working on updating the guidelines to use SPDX identifiers (and therefore SPDX expressions).
SPDX _expression_ logic is identical to Fedora's, so that will not change. The identifiers will be changing in phases, so the tool is useful today and it is definitely worth working through now.
SPDX _expression_ [1] are actually slightly better, because they have defined BNF grammar.
Currently used strings in the License tag, does not use any grammar at all. Every tool I know threat it as a string.
IIRC This [2] is the first approach to define the grammar. If/When me to SPDX _expression_, then we just update the file with grammar and (as Neal pointed out) everything else will not change.
With SPDX _expression_, we can use other tools. But e.g., `license-_expression_` [3] uses its own parser. And therefore is looong (2k lines of code). While license-validate has only 40 lines long.
[1
]https://spdx.github.io/spdx-spec/v2-draft/SPDX-license-expressions/
[2] https://pagure.io/copr/license-validate/blob/main/f/grammar.lark
[3] https://github.com/nexB/license-_expression_
Miroslav
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
