On Mon, Jun 29, 2026 at 12:25 PM Alexander Kanavin <[email protected]>
wrote:

> On Mon, 29 Jun 2026 at 20:18, Joshua Watt via lists.openembedded.org
> <[email protected]> wrote:
> > Thanks, but we can't actually use the license exceptions this way. The
> problem is that exceptions are only valid after an spdx `WITH` statement
> (e.g. "GPL-3.0 AND OpenSSL-exception" is not valid), which our license
> expressions do not support. Also, it's better to keep the licenses and
> exceptions in separate files so that it's easier to distinguish them when
> parsing.
> >
> > Regardless, I have been working on converting all our license
> expressions to valid SPDX expressions, but it got sidetracked by some SBoM
> work. Part of that was somewhat similar patch to fetch the exceptions. If
> you would like to take a look, the branch is contrib/jpew/spdx-licenses. I
> hope to get back to working on that as soon as the SBoM stuff is sorted out.
>
> A related issue is that lack of support for SPDX exceptions holds up
> correctly specifying fmt's license terms (which is 'MIT WITH
> fmt-exception' if I understood you right):
>
> https://spdx.org/licenses/fmt-exception.html
> https://github.com/fmtlib/fmt/blob/main/doc/LICENSE-exception
>
> The current recipe says simply 'MIT'.
>

Correct. In the short term, you can make a new "OE" license that is
"MIT-with-fmt-exception" to capture this (we have examples of this already,
see Apache-2.0-with-LLVM-exception), and then once my changes are in you
can change to the correct SPDX expression "MIT WITH fmt-exception"


>
> Alex
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#239821): 
https://lists.openembedded.org/g/openembedded-core/message/239821
Mute This Topic: https://lists.openembedded.org/mt/120005594/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to