Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Tasslehoff Kjappfot <tasskjapp@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: License attributions for a system built with OpenEmbedded.
Date: Tue, 15 May 2012 13:24:19 +0100	[thread overview]
Message-ID: <53487189.7itrN9qUEW@helios> (raw)
In-Reply-To: <4FB23F7C.1060302@gmail.com>

On Tuesday 15 May 2012 13:35:24 Tasslehoff Kjappfot wrote:
> I've already written that I use OpenEmbedded as a build system, and
> included the MIT license. I also used create_manifest.sh from Arago to
> get a list of everything included in the rootfs. What I really wonder is
> if I must add all that information as well.

[Disclaimer: I'm not a lawyer, this is not legal advice, etc.]

Ultimately you have to comply with the terms set out in the licenses of the 
code you're distributing. For example, if those licenses require you to 
provide the source code (or a written offer for same) regardless of whether you 
have changed the source or not, then that's what you have to do for the 
software you distribute under that license.

At the very least you should check all of the licenses to make sure you 
understand your obligations.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2012-05-15 12:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 12:02 License attributions for a system built with OpenEmbedded Tasslehoff Kjappfot
2012-05-14 21:24 ` Khem Raj
2012-05-15 11:35   ` Tasslehoff Kjappfot
2012-05-15 12:24     ` Paul Eggleton [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=53487189.7itrN9qUEW@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=tasskjapp@gmail.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