From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <Openembedded-devel@lists.openembedded.org>
Subject: Re: mpg123 recipe LICENSE_FLAGS = "commercial" issue
Date: Wed, 17 Sep 2014 09:09:17 +0200 [thread overview]
Message-ID: <5419339D.5060807@pseudoterminal.org> (raw)
In-Reply-To: <CAMKF1src0wJ6vStvRp1sJdpRy_tf-=FDcz_LMdAoA-QsgrE_Gg@mail.gmail.com>
On 2014-09-17 02:20, Khem Raj wrote:
>
>
> On Tuesday, September 16, 2014, Carlos Rafael Giani
> <dv@pseudoterminal.org <mailto:dv@pseudoterminal.org>> wrote:
>
> On 2014-09-16 07:43, Khem Raj wrote:
>
> Hi Carlos/All
>
> I want to understand why LICENSE_FLAGS = "commercial" was added to
>
> meta-multimedia/recipes-multimedia/mpg123/mpg123_1.15.3.bb
> <http://mpg123_1.15.3.bb>
>
> in initial commit and has been carried over upgrades ever since
>
> The license seems to be LGPL 2.0 and is explained in greater
> detail here
>
> http://mpg123.org/cgi-bin/scm/mpg123/trunk/doc/ROAD_TO_LGPL?revision=2607
>
> So what portions of it are having different terms for
> commercial distribution ?
>
> Thanks
>
> -Khem
>
>
> It's because MPEG audio is subject to royalties
>
>
> In what way where the component is lgpl I would like to understand
>
> This is also the reason why gst-plugins-ugly and
> gstreamer1.0-plugins-ugly have this flag.
>
> Carlos
>
*mpg123* is LGPL. But mpg123 is an implementation of an MPEG 1 audio
layer 1/2/3 and MPEG 2 audio. MPEG-1 layer 3 is what everybody calls
mp3. (mp1 and mp2 are pretty much dead by now.) mp3 itself contains
patents, and these are subject to royalties. Technicolor (formerly
Thomson) does enforce these royalties. See
http://mp3licensing.com/royalty/software.html for their price model.
MPEG-2 is controlled by the MPEG LA.
Note that these royalties cover the audio technology itself (say, mp3),
*not* the implementations. Implementations themselves can be subject to
any license, it's up to the authors of the implementations. But if you
actually want to use these implementations in a commercial product,
you'll have to pay the royalty fees.
This is part of the reason why Ogg Vorbis (and Opus) exist. They are an
alternative that doesn't require such fees. Therefore, the Vorbis
decoder isn't in gst-plugins-ugly, but in gst-plugins-good.
prev parent reply other threads:[~2014-09-17 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 5:43 mpg123 recipe LICENSE_FLAGS = "commercial" issue Khem Raj
2014-09-16 9:11 ` Carlos Rafael Giani
2014-09-16 21:33 ` Denys Dmytriyenko
2014-09-16 22:48 ` Carlos Rafael Giani
2014-09-17 0:20 ` Khem Raj
2014-09-17 7:09 ` Carlos Rafael Giani [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=5419339D.5060807@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.