Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: inconsistency with adding LICENSE lines to images
Date: Fri, 27 Feb 2015 15:58:32 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1502271553110.8885@localhost> (raw)


  just noticed the following ... in OE image definition files under
recipes-core:

core-image-base.bb
core-image-minimal.bb
core-image-minimal-dev.bb
core-image-minimal-initramfs.bb
core-image-minimal-mtdutils.bb

it *seems* to make sense that image definitions that require or
include other core image bb files don't need to add the line:

LICENSE = "MIT"

as they pick it up from the include'd or require'd file, but image
recipe files that

inherit core-image

*do* need to define their own license.

  but if one then goes under recipes-extended/images, it looks a bit
strange as, for example, here's core-image-full-cmdline.bb:

DESCRIPTION = "A console-only image with more full-featured Linux system \
functionality installed."

IMAGE_FEATURES += "splash ssh-server-openssh"

IMAGE_INSTALL = "\
    packagegroup-core-boot \
    packagegroup-core-full-cmdline \
    ${CORE_IMAGE_EXTRA_INSTALL} \
    "

inherit core-image

  so ... what's the licensing there? this image inherits directly from
core-image, but doesn't define a license? am i misunderstanding the
need for a license?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


             reply	other threads:[~2015-02-27 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 20:58 Robert P. J. Day [this message]
2015-03-03 11:25 ` inconsistency with adding LICENSE lines to images Paul Eggleton
2015-03-03 12:54   ` Flanagan, Elizabeth

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=alpine.LFD.2.11.1502271553110.8885@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@lists.openembedded.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