[yocto] How to deal with non-standard license.

Flanagan, Elizabeth elizabeth.flanagan at intel.com
Tue Jun 11 15:10:42 PDT 2013


On Tue, Jun 11, 2013 at 5:28 AM, Diego <diego.ml at zoho.com> wrote:
> Hi everybody,
>
> I have written a recipe which I'd like to contribute for glmark2:
> https://launchpad.net/glmark2
>
> The last thing that puzzles me before submitting it is that it's partly GPL3+,
> and partly under this license:
> https://github.com/rafalmiel/glmark2-wl/blob/master/COPYING.SGI
> which is not in this list:
> https://wiki.yoctoproject.org/wiki/License_Infrastructure_Interest_Group#Licenses
> Is there any way to deal with that license? What should I put in the LICENSE
> field in my recipe?

So, you will need to add a custom license or submit a patch OE-Core to
add that license. Where are you contributing this to?

If it's to a layer, you'll want to add the license to a custom license
path. You'll want that file to be unique and descriptive. Please make
sure the license filename has a version in the file name. eg SGI-1.
Within the layer you'll make a directory (in this example I use
custom-licenses), add the license text to a file named SGI-1, then add
this to your layer.conf:

LICENSE_PATH += "${LAYERDIR}/custom-licenses"
SPDXLICENSEMAP[SGIv1] = "SGI-1"

That should get you what you want.

-b

>
> Bests,
> Diego
>
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
Elizabeth Flanagan
Yocto Project
Build and Release



More information about the yocto mailing list