Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] LICENSE: Clarify what is meant by 'metadata'
Date: Tue, 28 Feb 2017 07:13:26 -0800	[thread overview]
Message-ID: <1488294806.22952.60.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LaWEDCdoRcS+GrBkW7D=xW7dPLn9VWKP9MkzkSmNCA7og@mail.gmail.com>

On Mon, 2017-02-27 at 20:59 +0000, Burton, Ross wrote:
> 
> On 27 February 2017 at 16:24, Saul Wold <sgw@linux.intel.com> wrote:
> > The term metadata in the LICENSE text is unclear and recently
> > garnered some questions at ELC, so clarify metadata to include
> > bbclasses, which is and has been metadata as well as code.
> > 
> > Signed-off-by: Saul Wold <sgw@linux.intel.com>
> > 
> 
> This breaks other layers (including meta-intel and meta-qt), do you
> have corresponding patches?
> 
Oh man, I did not consider recipes using the OE-Core LICENSE file as a
LIC_CHKSUM_FILE, that's sort of wrong on almost all cases except maybe
the build-appliance or some containers that also contain OE-Core meta-
data.

Layers particularly should not use OE-Core's LICENSE, so fixes to
layers will go first.

V2 coming when those are merged.

Sau!

> Ross


      reply	other threads:[~2017-02-28 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 16:24 [PATCH] LICENSE: Clarify what is meant by 'metadata' Saul Wold
2017-02-27 20:59 ` Burton, Ross
2017-02-28 15:13   ` Saul Wold [this message]

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=1488294806.22952.60.camel@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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