Dne 14. 03. 23 v 14:47 Michael Catanzaro napsal(a):
Even if you somehow succeed once, ***your result will become stale each time the package gets rebased***. We're real
bad at keeping the existing *simple* license fields updated so there's just no way we'll be able to handle the complex
version.
Good point. And we already raised this point several times on our meetings (SPDX Change owners mtgs).
The problem is that what you describe are two big steps. First one - migrate to SPDX identifiers. Second one - make sure
that the identifiers are correct on every update.
Mixing these two steps together will results in delivering *both* steps much much later. BTW for the step two - we
already have idea to use Cavil [1]. But if we would do both steps at the same time, that means we have to set up Cavil
to recognize both SPDX ids and the Fedora's legacy shortnames. That means more work, and longer delivery time.
So right now, the plan is to finish migration to SPDX ids. Accept the risk that some license string may diverge in
meantime (which is btw no change from current and past situation). And when we are done with the first step only then
continue with process of auditing the license field on every rebase. Actually likely on every commit in dist-git.
[1] https://github.com/openSUSE/cavil
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, report it: https://pagure.io/fedora-infrastructure/new_issue
