At some point we added a rule, “A license should normally appear only once in the License: tag license expression. But if the license expression includes an OR sub-expression, that OR sub-expression is treated as though it were a single license for purposes of this rule. *****As an exception to this rule, if all the license operands of the OR sub-expression also appear in the license expression outside the OR sub-expression, then you can eliminate the OR sub-expression.*****” https://docs.fedoraproject.org/en-US/legal/license-field/#_special_rules_for_or_expressions I don’t like this rule, because: - I don’t like the cognitive burden on packagers of adding another step away from pure, straightforward mechanical enumeration of licenses - I believe the simplification discards useful information - I think it’s not clear exactly how it should be interpreted in complicated, possibly nested SPDX expressions Nevertheless, this rule would appear to specifically allow the simplification you described. On Sat, Aug 17, 2024, at 3:12 PM, Miroslav Suchý wrote: > Dne 17. 08. 24 v 8:02 odp. Dridi Boukelmoune napsal(a): >> I ended up with the following license tag that I moved to SPDX as part >> of the incoming update: >> >> License: GPL-2.0-only AND MIT AND (GPL-2.0-only OR MIT) >> >> I feel like I could technically factor it to just "GPL-2.0-only AND >> MIT" because picking either license in the dual-licensed js script >> will effectively result in just that, but I kept the expanded license >> tag to reflect the presence of a dual-licensed piece of software (and >> because I saw nothing resembling this case in the guidelines). >> >> What is the preferred expression here? Are they both correct? > https://docs.fedoraproject.org/en-US/legal/license-field/#_no_effective_license_analysis > > "you should not attempt to simplify or reduce the License tag" > > So full license expression is correct. I.e. > > GPL-2.0-only AND MIT AND (GPL-2.0-only OR MIT) > in your case. > > > > -- > Miroslav Suchy, RHCA > Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys > -- > _______________________________________________ > 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 -- _______________________________________________ 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
