Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org,
	Olaf Mandel <o.mandel@menlosystems.com>
Subject: Re: [PATCH 0/1] $COREBASE/LICENSE in LIC_FILES_CHKSUM
Date: Fri, 21 Oct 2016 10:36:53 -0400	[thread overview]
Message-ID: <20161021143653.GC2494@denix.org> (raw)
In-Reply-To: <1985222.nRgBkrL9KW@peggleto-mobl.ger.corp.intel.com>

On Fri, Oct 21, 2016 at 12:29:55PM +1300, Paul Eggleton wrote:
> Hi Olaf,
> 
> On Wed, 19 Oct 2016 10:05:12 Olaf Mandel wrote:
> > I ran into QA issues when inadvertently replacing OEs LICENSE with
> > Yoctos LICENSE file. Why should recipes depend on the license for
> > the complete collection of layers? At least for "normal" recipes
> > that generate target device packages, this makes no sense to me.
> > 
> > I patched out the global LICENSE file from all those recipes that
> > are short enough and where I feel reasonably confident of not
> > having actually changed the claimed license terms in any way.
> 
> Agreed, doing this cleanup makes sense to me. We should especially discourage
> others from referring to this file in their own recipes, and we start by
> showing a good example.

FWIW, we also discussed this topic at OEDEM last week...


> > There are additional recipes that reference the global LICENSE
> > file, but where I am not sure if a less blanket license declaration
> > is appropriate or not. Especially for meta-toolchain and
> > build-appliance-image, the global LICENSE is probably correct.
> > Any comments?
> 
> For images and other recipes that don't pull in anything by themselves, there
> shouldn't be a need for LIC_FILES_CHKSUM (or indeed LICENSE) to be set at all
> - in order to understand the license for the result the appropriate place to
> look is the license manifest that represents everything that goes into the
> image. In fact, in master / morty, if SRC_URI is empty then LIC_FILES_CHKSUM
> is no longer verified [1]. Thus, for such recipes we can remove the setting of
> LIC_FILES_CHKSUM (and LICENSE, if possible) altogether.
> 
> Cheers,
> Paul
> 
> [1] http://cgit.openembedded.org/openembedded-core/commit/?id=c269547ae8e90a78349f6003385137e4145e145f
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


  parent reply	other threads:[~2016-10-21 14:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 10:05 [PATCH 0/1] $COREBASE/LICENSE in LIC_FILES_CHKSUM Olaf Mandel
2016-10-19 10:05 ` [PATCH 1/1] Remove $COREBASE/LICENSE from LIC_FILES_CHKSUM Olaf Mandel
2016-10-20 10:44   ` Peter Kjellerstedt
2016-10-20 11:11     ` Olaf Mandel
2016-10-21  9:24   ` [PATCH v2] " Olaf Mandel
2016-10-20 23:29 ` [PATCH 0/1] $COREBASE/LICENSE in LIC_FILES_CHKSUM Paul Eggleton
2016-10-21 14:05   ` Olaf Mandel
2016-10-21 14:36   ` Denys Dmytriyenko [this message]
2016-10-21 19:36   ` Paul Eggleton
  -- strict thread matches above, loose matches on Subject: below --
2016-10-21  9:24 Forgot Signed-off-by lines Olaf Mandel
2016-10-17 16:23 ` [PATCH] combo-layer: handle file_exclude matching dirs Olaf Mandel
2016-10-21  9:24   ` [PATCH v2] " Olaf Mandel

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=20161021143653.GC2494@denix.org \
    --to=denis@denix.org \
    --cc=o.mandel@menlosystems.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox