All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Quentin Schulz <foss+buildroot@0leil.net>
Cc: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package: pcsc-lite: pcsc_demo is under BSD-3-Clause and not GPL-3.0-or-later
Date: Tue, 19 Jul 2022 18:33:50 +0200	[thread overview]
Message-ID: <20220719163350.GN2249625@scaer> (raw)
In-Reply-To: <20220719133144.2787205-1-foss+buildroot@0leil.net>

Quentin, All,

On 2022-07-19 15:31 +0200, Quentin Schulz spake thusly:
> From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> 
> Since commit b01f19fb9361 ("pcsc_demo: change licence from GPLv3 to
> BSD") in pcsclite, the license of pcsc_demo is BSD-3-Clause and not
> GPL-3.0-or-later, so let's update the package license information.
> 
> Cc: Quentin Schulz <foss+buildroot@0leil.net>
> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
> 
> Cc'ing Peter as maintainer of stable branches since this commit can be
> backported to 2022.02.x and 2022.05.x branches since the commit in
> pcsclite is in the tree since 1.9.2 (and 2022.02.x has 1.9.5).
> 
>  package/pcsc-lite/pcsc-lite.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/pcsc-lite/pcsc-lite.mk b/package/pcsc-lite/pcsc-lite.mk
> index ad34bb4b90..d007d8da2f 100644
> --- a/package/pcsc-lite/pcsc-lite.mk
> +++ b/package/pcsc-lite/pcsc-lite.mk
> @@ -9,7 +9,7 @@ PCSC_LITE_SOURCE = pcsc-lite-$(PCSC_LITE_VERSION).tar.bz2
>  PCSC_LITE_SITE = https://pcsclite.apdu.fr/files
>  PCSC_LITE_INSTALL_STAGING = YES
>  PCSC_LITE_DEPENDENCIES = host-pkgconf host-flex
> -PCSC_LITE_LICENSE = BSD-2-Clause (auth), BSD-3-Clause, GPL-3.0+ (demo, spy, tests), ISC (simclist)
> +PCSC_LITE_LICENSE = BSD-2-Clause (auth), BSD-3-Clause, GPL-3.0+ (spy, tests), ISC (simclist)
>  PCSC_LITE_LICENSE_FILES = COPYING GPL-3.0.txt
>  PCSC_LITE_SELINUX_MODULES = pcscd
>  PCSC_LITE_CONF_OPTS = --disable-strict
> -- 
> 2.36.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-07-19 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 13:31 [Buildroot] [PATCH] package: pcsc-lite: pcsc_demo is under BSD-3-Clause and not GPL-3.0-or-later Quentin Schulz
2022-07-19 16:33 ` Yann E. MORIN [this message]
2022-08-11 11:12 ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220719163350.GN2249625@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=foss+buildroot@0leil.net \
    --cc=quentin.schulz@theobroma-systems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.