[OE-core] [PATCH 2/5] Add LICENSE_FLAGS to packages mentioned in COMMERCIAL_LICENSE

Phil Blundell philb at gnu.org
Fri Jan 6 17:15:29 UTC 2012


On Fri, 2012-01-06 at 10:45 -0600, tom.zanussi at intel.com wrote:
> diff --git a/meta/recipes-multimedia/gstreamer/gst-fluendo-mp3_0.10.16.bb b/meta/recipes-multimedia/gstreamer/gst-fluendo-mp3_0.10.16.bb
> index 5975513..0a90f9c 100644
> --- a/meta/recipes-multimedia/gstreamer/gst-fluendo-mp3_0.10.16.bb
> +++ b/meta/recipes-multimedia/gstreamer/gst-fluendo-mp3_0.10.16.bb
> @@ -2,6 +2,7 @@ require gst-fluendo.inc
>  
>  LICENSE = "MIT"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=98326cbb1723a5a97e9b1db62e9faa05"
> +LICENSE_FLAGS = "Commercial"

If I'm understanding the mechanism correctly then just setting all of
these to "Commercial" seems like a bit of a retrograde step.  Is there
an easy way in this new world for me to say that (for the sake of
argument) gst-fluendo-mp3 is acceptable for inclusion but libomixl
isn't?

It seems to me that, for this feature to be much use, the LICENSE_FLAGS
need to be a bit more explicit about spelling out what the requirements
really are for each package.  So, if the issue here is that you need to
pay the MP3 decoder licence on each unit you ship, let's say something
like LICENSE_FLAGS = "mp3-decoder-royalties" rather than just
"Commercial".

p.






More information about the Openembedded-core mailing list