All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Ross Burton <ross@burtonini.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD license
Date: Thu, 4 Nov 2021 11:19:22 +0000	[thread overview]
Message-ID: <ce5f46365f6d4d38a6017b04ee1564f0@axis.com> (raw)
In-Reply-To: <16B23C3CDA8BCB16.30289@lists.openembedded.org>

Ross: any comment to my question below?

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Peter Kjellerstedt
> Sent: den 28 oktober 2021 17:44
> To: Ross Burton <ross@burtonini.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD
> license
> 
> > -----Original Message-----
> > From: openembedded-core@lists.openembedded.org <openembedded-
> > core@lists.openembedded.org> On Behalf Of Ross Burton
> > Sent: den 2 september 2021 18:25
> > To: openembedded-core@lists.openembedded.org
> > Subject: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD
> > license
> >
> > "BSD" is ambiguous, use the precise licenses BSD-2-Clause BSD-4-Clause.
> >
> > Signed-off-by: Ross Burton <ross.burton@arm.com>
> > ---
> >  meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > index 7519b4c018d..e53ccc6aea8 100644
> > --- a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > +++ b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > @@ -8,7 +8,7 @@ python () {
> >
> >  require xorg-lib-common.inc
> >
> > -LICENSE = "MIT & MIT-style & BSD"
> > +LICENSE = "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
> 
> Why is this marked as BSD-4-Clause? Looking at the COPYING file and
> searching the code I can find no trace of any license text with the
> advertising clause from BSD-4-Clause. What am I missing?
> 
> >  LIC_FILES_CHKSUM =
> "file://COPYING;md5=172255dee66bb0151435b2d5d709fcf7"
> >
> >  SRC_URI[md5sum] = "c5fa5a86a20e3591bed6c046498d4b8f"
> > --
> > 2.25.1
> 
> //Peter

//Peter



  parent reply	other threads:[~2021-11-04 11:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 16:24 [PATCH 01/14] lz4: remove redundant BSD license Ross Burton
2021-09-02 16:24 ` [PATCH 02/14] python3-numpy: " Ross Burton
2021-09-02 16:24 ` [PATCH 03/14] quota: remove " Ross Burton
2021-09-02 16:24 ` [PATCH 04/14] nfs-utils: set precise " Ross Burton
2021-09-02 16:24 ` [PATCH 05/14] dtc: " Ross Burton
2021-09-02 16:24 ` [PATCH 06/14] acpica: " Ross Burton
2021-09-02 16:24 ` [PATCH 07/14] libevent: " Ross Burton
2021-09-02 16:24 ` [PATCH 08/14] openssh: remove redundant " Ross Burton
2021-09-02 16:24 ` [PATCH 09/14] python3-packaging: fix license statement Ross Burton
2021-09-02 16:24 ` [PATCH 10/14] iputils: set precise BSD license Ross Burton
2021-09-02 16:24 ` [PATCH 11/14] libx11-compose-data: " Ross Burton
2021-10-28 15:44   ` [OE-core] " Peter Kjellerstedt
     [not found]   ` <16B23C3CDA8BCB16.30289@lists.openembedded.org>
2021-11-04 11:19     ` Peter Kjellerstedt [this message]
2021-11-04 11:33       ` Ross Burton
2021-11-04 14:47         ` Joshua Watt
2021-09-02 16:24 ` [PATCH 12/14] webkitgtk: " Ross Burton
2021-09-02 16:24 ` [PATCH 13/14] libwpe: " Ross Burton
2021-09-02 16:24 ` [PATCH 14/14] wpebackend-fdo: " Ross Burton

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=ce5f46365f6d4d38a6017b04ee1564f0@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross@burtonini.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.