meta-wolfssl/recipes-wolfssl/wolfpkcs11
Mark Atwood 8d24ad250c fix: correct recipe licenses to match upstream sources
Every recipe below builds sources whose headers say "or (at your
option) any later version", so none is -only.

- 15 recipes GPL-3.0-only -> GPL-3.0-or-later (wolfssl, linuxkm,
  wolfcrypttest/benchmark, wolfprovider(+cmd/test), wolfengine,
  wolfssh, wolfpkcs11, wolfhsm, wolfboot, wolftpm, wolfcrypt-py)
- wolfmqtt, wolfclu: GPL-2.0-only -> GPL-3.0-or-later (sources are
  v3+). wolfclu checksum moved from LICENSE (GPLv2 text) to COPYING
  (GPLv3 text) at the pinned rev.
- wolfssl-py, wolf-py-tests, wolftpm-wrap-test: GPL-2.0-only ->
  GPL-2.0-or-later (sources at those pins are v2+).
- README: wolfSSL is GPLv3 (or later), not GPLv2.

Unchanged: fips-ready recipes (source is a user-supplied bundle) and
wolfssl-gnutls-wrapper (upstream has no license file).
2026-10-06 13:19:28 -07:00
..
commercial Ensure target directory exists for dummy autogen.sh file in do_configure_disable_autogen. 2026-04-29 17:06:04 -07:00
wolfpkcs11_2.0.0.bb fix: correct recipe licenses to match upstream sources 2026-10-06 13:19:28 -07:00
wolfssl_%.bbappend Refactor finalization (#149) 2026-02-02 15:43:35 -07:00