public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Meh Mbeh Ida Delphine <idadelm@gmail.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [poky-contrib][RFC PATCH 2/5] package: Remove false positive lic warnings
Date: Wed, 17 Feb 2021 14:55:50 +0000	[thread overview]
Message-ID: <008095bfe41a468ba2d5fb3ba06160eb@XBOX03.axis.com> (raw)
In-Reply-To: <8bb8d2888759c8102ee35a7b3badf06fdb0eea86.camel@linuxfoundation.org>

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 17 februari 2021 11:40
> To: Meh Mbeh Ida Delphine <idadelm@gmail.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [poky-contrib][RFC PATCH 2/5] package: Remove false
> positive lic warnings
> 
> On Wed, 2021-02-17 at 05:00 +0100, Meh Mbeh Ida Delphine wrote:
> > With the IGNOREWITHLINUXSYSCALLNOTE variable set to "1" in local.conf,
> it removes the "WITH Linux syscall note" string attached to the license
> value for sources before comparism.
> > This is to get more recipe LICENSES to match with those of the sources
> and reduce the number of warnings outputed.
> >
> > Signed-off-by: Ida Delphine <idadelm@gmail.com>
> > ---
> >  meta/classes/package.bbclass | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
> > index c3259146b6..14c8475cfa 100644
> > --- a/meta/classes/package.bbclass
> > +++ b/meta/classes/package.bbclass
> > @@ -1774,6 +1774,10 @@ fi
> >                      if l.endswith('-or-later'):
> >                          lic_ = l.replace('-or-later', '+')
> >                          computedpkglicsperpkg.add(lic_)
> > +                    elif l.endswith(' WITH Linux-syscall-note'):
> > +                        if d.getVar("IGNOREWITHLINUXSYSCALLNOTE") == "1":
> > +                            lic_ = l.replace(' WITH Linux-syscall-note', '')
> > +                            computedpkglicsperpkg.add(lic_)
> 
> I think this is going to break things and it should be entirely
> removing this license entry.
> 
> Why? Headers under GPLv2 WITH Linux-syscall-note can be used in a non-
> GPLv2 application and that application doesn't then become under GPLv2.
> 
> What we probably want is a "safe" list of licenses which don't have
> implications and entries matching "* WITH Linux-syscall-note" can be
> ignored, as long as they're only in header files. Perhaps we also need
> a check to ensure we only see "* WITH Linux-syscall-note" in header
> files?
> 
> Cheers,
> 
> Richard

Isn't the problem here really the multiple (sometimes contradictory) use 
cases for the LICENSE variable. 

1) It is used to document the licenses that cover the code.
2) It is used to determine if the recipe can be built.
3) It is used (together with LIC_FILES_CHKSUM) to populate the licenses that 
   go into, e.g., ${PN}-lic.
4) It is used by archiver.bbclass to determine what code to export.

To comply with 1) and 3), you want to include, e.g., "GPL-3.0 WITH 
Linux-syscall-note", but for 2) and 4), you probably do not want it. 

Related to this is also recipes that have a LICENSE such as "Foo | Bar" 
where there is a choice as to which license we as a publisher of binaries 
choose when distributing the code. Since this choice may vary from 
distributor to distributor it is not as simple as to just list them both.

//Peter


  reply	other threads:[~2021-02-17 14:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17  4:00 [poky-contrib][RFC PATCH 0/5] Suggestions for improvements? Meh Mbeh Ida Delphine
2021-02-17  4:00 ` [poky-contrib][RFC PATCH 1/5] package: Remove false positive lic warnings Meh Mbeh Ida Delphine
2021-02-17 10:42   ` [OE-core] " Richard Purdie
2021-02-17  4:00 ` [poky-contrib][RFC PATCH 2/5] " Meh Mbeh Ida Delphine
2021-02-17 10:39   ` [OE-core] " Richard Purdie
2021-02-17 14:55     ` Peter Kjellerstedt [this message]
2021-02-17 15:04       ` Richard Purdie
2021-02-17  4:00 ` [poky-contrib][RFC PATCH 3/5] " Meh Mbeh Ida Delphine
2021-02-17  4:00 ` [poky-contrib][RFC PATCH 4/5] license.bbclass: Add functions to split and canonicalise license strings Meh Mbeh Ida Delphine
2021-02-17 10:45   ` [OE-core] " Richard Purdie
2021-02-17 15:04   ` Peter Kjellerstedt
2021-02-17 16:36     ` Richard Purdie
2021-02-17 16:55       ` Meh Mbeh Ida Delphine
2021-02-17 20:51         ` Richard Purdie
2021-02-21  3:04           ` Meh Mbeh Ida Delphine
2021-02-21 11:21             ` Richard Purdie
2021-02-17  4:00 ` [poky-contrib][RFC PATCH 5/5] package.bbclass: Remove false positive license warnings Meh Mbeh Ida Delphine
2021-02-17 15:50 ` [OE-core] [poky-contrib][RFC PATCH 0/5] Suggestions for improvements? Peter Kjellerstedt
2021-02-17 16:58   ` Meh Mbeh Ida Delphine
2021-02-18 11:17     ` Peter Kjellerstedt
2021-02-18 12:21       ` Meh Mbeh Ida Delphine

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=008095bfe41a468ba2d5fb3ba06160eb@XBOX03.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=idadelm@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox