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