From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: mpg123 recipe LICENSE_FLAGS = "commercial" issue
Date: Tue, 16 Sep 2014 17:33:43 -0400 [thread overview]
Message-ID: <20140916213343.GW2480@denix.org> (raw)
In-Reply-To: <5417FED2.1030106@pseudoterminal.org>
On Tue, Sep 16, 2014 at 11:11:46AM +0200, Carlos Rafael Giani 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
> >
> >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. This is also the
> reason why gst-plugins-ugly and gstreamer1.0-plugins-ugly have this
> flag.
But does gst-plugins-ugly provide own codecs? It's mostly a collection of
external plugins, so it shouldn't itself be marked as "commercial":
http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/51055
--
Denys
next prev parent reply other threads:[~2014-09-16 22:34 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 [this message]
2014-09-16 22:48 ` Carlos Rafael Giani
2014-09-17 0:20 ` Khem Raj
2014-09-17 7:09 ` Carlos Rafael Giani
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=20140916213343.GW2480@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@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 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.