Re: [oe-core][master][PATCH] libgcrypt: Update license for dbg package

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2026-09-17 at 13:36 +0530, Sana Kazi via lists.openembedded.org wrote:
> From: Sana Kazi <Kazi.S@bmwtechworks.in>
> 
> Set LICENSE for libgcrypt-dbg as "LGPL-2.1-or-later"
> as the files used in dbg package use LGPL-2.1-or-later.
> 
> Signed-off-by: Sana Kazi <Kazi.S@bmwtechworks.in>
> ---
>  meta/recipes-support/libgcrypt/libgcrypt_1.12.4.bb | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/recipes-support/libgcrypt/libgcrypt_1.12.4.bb b/meta/recipes-support/libgcrypt/libgcrypt_1.12.4.bb
> index 1b2b1dc13b..27b9d7fa15 100644
> --- a/meta/recipes-support/libgcrypt/libgcrypt_1.12.4.bb
> +++ b/meta/recipes-support/libgcrypt/libgcrypt_1.12.4.bb
> @@ -9,6 +9,7 @@ SECTION = "libs"
>  LICENSE = "BSD-3-Clause AND GPL-2.0-or-later AND LGPL-2.1-or-later"
>  LICENSE:${PN} = "BSD-3-Clause AND LGPL-2.1-or-later"
>  LICENSE:${PN}-dev = "GPL-2.0-or-later AND LGPL-2.1-or-later"
> +LICENSE:${PN}-dbg = "LGPL-2.1-or-later"
>  
>  LIC_FILES_CHKSUM = "file://COPYING;md5=570a9b3749dd0463a1778803b12a6dce \
>                      file://COPYING.LIB;md5=4bf661c1e3793e55c8d1051bc5e0ae21 \

How are you deciding that none of the files in the -dbg package are
under just that license? The cipher/sha* files are likely a issue on at
least some architectures at the very least?

Cheers,

Richard