Hi Miroslav: You wrote: > Tooling will acomodate to specification. Sooner or later. > > It is harder with people. I am doing regular checks how we are doing with > transition to SPDX ids in Fedora. Most of the errors are in case sensitivity > of operators. There is no tooling that can craft the license string for a > package. There are some assisting tools, but at the end human write the > license string. And they are not SPDX specification experts - so they often > write and/or.
https://pypi.org/project/license-expression/ may be useful in this case: It can take a weird expression and then validate and fix the case of identifiers and operators to return a correct, canonical expression. You could write a small tool to fix or lint spec files with it. It is somewhat popular and is used in tools like REUSE, ScanCode, and SPDX tools among others. It is downloaded about 50,000 times each day. /hth -- Cordially Philippe Ombredanne -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1812): https://lists.spdx.org/g/spdx/message/1812 Mute This Topic: https://lists.spdx.org/mt/102715215/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/spdx/leave/2655439/21656/1698928721/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
