From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>, Joshua Watt <jpewhacker@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 4/4] faad2: set LICENSE_FLAGS
Date: Fri, 22 Mar 2019 12:32:06 +1300 [thread overview]
Message-ID: <1698450.TmOFBMJAC0@localhost.localdomain> (raw)
In-Reply-To: <CAMKF1sprBWXWR2b13ARFOK8LYSjrkbiyx_cWDfKXUktUhZOzdQ@mail.gmail.com>
On Friday, 22 March 2019 10:29:13 AM NZDT Khem Raj wrote:
> On Thu, Mar 21, 2019 at 2:09 PM Joshua Watt <jpewhacker@gmail.com> wrote:
> >
> > On Mon, 2018-08-13 at 19:50 +0200, Paul Eggleton wrote:
> > > Commercial usage requires a license according to the homepage, so set
> > > LICENSE_FLAGS = "commercial" to indicate that.
> > >
> > > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> > > ---
> > > meta-oe/recipes-multimedia/faad2/faad2_2.7.bb | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/meta-oe/recipes-multimedia/faad2/faad2_2.7.bb b/meta-
> > > oe/recipes-multimedia/faad2/faad2_2.7.bb
> > > index b777831ad..9e5a3817a 100644
> > > --- a/meta-oe/recipes-multimedia/faad2/faad2_2.7.bb
> > > +++ b/meta-oe/recipes-multimedia/faad2/faad2_2.7.bb
> > > @@ -5,6 +5,8 @@ LICENSE = "GPLv2"
> > >
> > > LIC_FILES_CHKSUM =
> > > "file://COPYING;md5=381c8cbe277a7bc1ee2ae6083a04c958"
> > >
> > > +LICENSE_FLAGS = "commercial"
> > > +
> >
> > My understanding was that faad2 was GPLv2, but you could *optionally*
> > get a commercial license for it if you needed one. Is the LICENSE_FLAG
> > necessary in that case? It seems like the default license of GPLv2
> > would apply unless you worked something out with them to get a
> > commercial license?
>
> Sometimes the use determines the license enforcement. e.g. it might
> be GPLed for personal use but not for selling products.
Also, the GPL unfortunately is not the only concern if you read the full
upstream README. I think it's best to err on the side of caution, after all
there is the ability for to set LICENSE_FLAGS_WHITELIST signifying "yes I have
checked and my usage is OK".
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2019-03-21 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 17:50 [meta-oe][PATCH 0/4] Minor faad2/faac fixes Paul Eggleton
2018-08-13 17:50 ` [meta-multimedia][PATCH 1/4] faac: set HOMEPAGE Paul Eggleton
2018-08-13 17:50 ` [meta-multimedia][PATCH 2/4] faac: set LICENSE_FLAGS Paul Eggleton
2018-08-13 17:50 ` [meta-oe][PATCH 3/4] faad2: set more accurate SUMMARY and add HOMEPAGE Paul Eggleton
2018-08-13 17:50 ` [meta-oe][PATCH 4/4] faad2: set LICENSE_FLAGS Paul Eggleton
2019-03-21 21:09 ` Joshua Watt
2019-03-21 21:29 ` Khem Raj
2019-03-21 23:32 ` Paul Eggleton [this message]
2019-03-22 2:49 ` Khem Raj
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=1698450.TmOFBMJAC0@localhost.localdomain \
--to=paul.eggleton@linux.intel.com \
--cc=jpewhacker@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@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