From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] libav: set LICENSE and LICENSE_FLAGS according to PACKAGECONFIG options
Date: Wed, 16 Jul 2014 10:31:01 +0200 [thread overview]
Message-ID: <53C63845.2060407@opendreambox.org> (raw)
In-Reply-To: <8672BB614B4CCA40A6B3BDD6FD82050BA8B27F6E@COSNADEXC13.usr.ingenico.loc>
On 16.07.2014 08:43, Matthieu CRAPET wrote:
> Hi again,
>
>> Some optional parts of Libav are licensed under the GNU General Public License version 2 or later (GPL v2+). See the file COPYING.GPLv2 for details.
>> None of these parts are used by default, you have to explicitly pass --enable-gpl to configure to activate them. In this case, Libav's license changes to GPL v2+."
>
> I may misunderstood something here.
>
> For example:
> - libavfiler. It contains yadif code which is GPLv2+ and frei0r code is LGPLv2.1+. Libavfiler is clearly contaminated:
Yadif needs to be enabled explicitly with --enable-gpl. frei0r is
disabled by default. If enabled, it's linked at runtime using dlopen.
At least, this is what the 'configure' script suggests.
> LICENSE_libavfilter = "GPLv2+"
> - libavutils is 100% LGPL
> LICENSE_libavutils = " LGPLv2.1+"
>
> Giving --enable-gpl to configure does not convert pure 100% LGPL licensed library to GPL license. Am I wrong?
If you combine GPL'ed and LGPL'ed code, the resulting binary will be GPL'ed.
https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License#Compatibility
Regards,
Andreas
next prev parent reply other threads:[~2014-07-16 8:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 14:23 [PATCH v2] libav: add PACKAGECONFIG for theora, libvorbis, speex and openssl Matthieu Crapet
2014-06-30 16:40 ` Martin Jansa
2014-07-01 7:31 ` Matthieu CRAPET
2014-07-11 6:36 ` Koen Kooi
2014-07-11 11:47 ` Matthieu CRAPET
2014-07-11 12:43 ` Andreas Oberritter
2014-07-15 14:38 ` Matthieu CRAPET
2014-07-15 14:54 ` [PATCH v3] libav: set LICENSE and LICENSE_FLAGS according to PACKAGECONFIG options Matthieu Crapet
2014-07-15 16:39 ` Andreas Oberritter
2014-07-16 6:43 ` Matthieu CRAPET
2014-07-16 8:31 ` Andreas Oberritter [this message]
2014-07-16 8:42 ` Andreas Oberritter
2014-07-16 9:05 ` Matthieu CRAPET
2014-07-16 16:31 ` Saul Wold
2014-07-17 14:44 ` [RFC][PATCH v4] libav: set LICENSE " Matthieu Crapet
2014-07-17 14:50 ` Matthieu CRAPET
2014-07-28 12:06 ` [PATCH] libav: fix PACKAGECONFIG for theora and libvorbis Matthieu Crapet
2014-07-28 12:10 ` Matthieu CRAPET
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=53C63845.2060407@opendreambox.org \
--to=obi@opendreambox.org \
--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