[oe] mpg123 recipe LICENSE_FLAGS = "commercial" issue

[Carlos Rafael Giani]

On 2014-09-16 23:33, Denys Dmytriyenko wrote:
> 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
>

But the whole point of gst-plugins-ugly is to be a collection of tested 
high-quality plugins for formats and standards which are subject to 
royalties. Tested quality plugins without the royalty go to -good.