How to deal with non-standard license.
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?
Bests,
Diego
Quoted 5 lines · Diego
Hi everybody,
I have written a recipe which I'd like to contribute for glmark2:
https://launchpad.net/glmark2
Quoted 7 lines
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
Quoted 8 lines
Bests,
Diego_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 3 lines
Elizabeth Flanagan Yocto Project Build and Release
In data martedì 11 giugno 2013 15:10:42, Flanagan, Elizabeth ha scritto:
Quoted 24 lines · Diego
Quoted 5 lines
Hi everybody,
I have written a recipe which I'd like to contribute for glmark2:
https://launchpad.net/glmark2Quoted 7 lines
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#L
icenses 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:
Quoted 4 lines
LICENSE_PATH+= "${LAYERDIR}/custom-licenses"
SPDXLICENSEMAP[SGIv1] = "SGI-1"That should get you what you want.
Hi Elizabeth,
I'm trying to integrate glmark2 into openembedded (meta-oe layer). I know this is not the right mailing list for that task, but I'm still on the license problem.
I've tried to do as you suggested, but I'm getting:
WARNING: glmark2: No generic license file exists for: SGI-1 in any provider Paul suggested:
LICENSE = "GPLv3+ & SGI-1"
I've tried also:
LICENSE = "GPLv3+ & SGIv1"
but I'm still getting the same error message (obviously with "SGIv1" instead).
I'm attaching the full patch for you to review if I'm doing something wrong.
Thank you for any hint you might give me,
Diego
From e050d390b053f4287634778e8ec3c7b582cd8b14 Mon Sep 17 00:00:00 2001
From: Diego Rondini <[email protected]>
Date: Wed, 12 Jun 2013 17:57:39 +0200
Subject: [meta-oe][PATCH] glmark2: Add recipe for glmark2
Add a recipe for glmark2, which is an OpenGL 2.0 / OpenGL ES 2.0 benchmark.
--- .../recipes-benchmark/glmark2/glmark2_2012.12.bb | 35 +++++++++++++++++ toolchain-layer/conf/layer.conf | 3 ++ toolchain-layer/custom-licenses/SGI-1 | 40 ++++++++++++++++++++ 3 files changed, 78 insertions(+) create mode 100644 meta-oe/recipes-benchmark/glmark2/glmark2_2012.12.bb create mode 100644 toolchain-layer/custom-licenses/SGI-1
meta-oe/recipes-benchmark/glmark2/glmark2_2012.12.bb new file +35 -0
@@ -0,0 +1,35 @@ +SUMMARY = "OpenGL (ES) 2.0 benchmark" +DESCRIPTION = "glmark2 is a benchmark for OpenGL (ES) 2.0. \ +It uses only the subset of the OpenGL 2.0 API that is compatible with OpenGL ES 2.0." +HOMEPAGE = "https://launchpad.net/glmark2" +BUGTRACKER = "https://bugs.launchpad.net/glmark2" + +LICENSE = "GPLv3+ & SGI-1" +LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \ + file://COPYING.SGI;md5=7125c8894bd29eddfd44ede5ce3ab1e4" + +DEPENDS = "libpng12" + +SRC_URI = "https://launchpad.net/${BPN}/trunk/${PV}/+download/${BP}.tar.gz" + +SRC_URI[md5sum] = "4f306664aa3886fa0cf93853603603f8" +SRC_URI[sha256sum] = "bea6f9de2cdce376195bd91e4a2fdfdf80bf3e480abff8e05b90a6458c1deb47" + +inherit pkgconfig + +PACKAGECONFIG ?= "gl gles2" + +PACKAGECONFIG[gl] = "--enable-gl,,virtual/libgl" +PACKAGECONFIG[gles2] = "--enable-glesv2,,virtual/libgles2" + +do_configure() { + ./waf configure --prefix=${prefix} ${EXTRA_OECONF} +} + +do_compile() { + ./waf build ${PARALLEL_MAKE} +} + +do_install() { + ./waf install --destdir=${D} +}
toolchain-layer/conf/layer.conf +3 -0
@@ -23,3 +23,6 @@ BBFILE_PATTERN_toolchain-layer := "^${LAYERDIR}/" BBFILE_PRIORITY_toolchain-layer = "6" +# Import custom license +LICENSE_PATH += "${LAYERDIR}/custom-licenses" +SPDXLICENSEMAP[SGIv1] = "SGI-1"
toolchain-layer/custom-licenses/SGI-1 new file +40 -0
@@ -0,0 +1,40 @@ +The data and some of the control logic for the "ideas" scene was adapted from +the "Ideas in Motion" GLUT demo. Per the rights granted by the source for that +demo, the following notice is reproduced here: + +/* + * (c) Copyright 1993, Silicon Graphics, Inc. + * ALL RIGHTS RESERVED + * Permission to use, copy, modify, and distribute this software for + * any purpose and without fee is hereby granted, provided that the above + * copyright notice appear in all copies and that both the copyright notice + * and this permission notice appear in supporting documentation, and that + * the name of Silicon Graphics, Inc. not be used in advertising + * or publicity pertaining to distribution of the software without specific, + * written prior permission. + * + * THE MATERIAL EMBODIED ON THIS SOFTWARE IS PROVIDED TO YOU "AS-IS" + * AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, + * INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR + * FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SILICON + * GRAPHICS, INC. BE LIABLE TO YOU OR ANYONE ELSE FOR ANY DIRECT, + * SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY + * KIND, OR ANY DAMAGES WHATSOEVER, INCLUDING WITHOUT LIMITATION, + * LOSS OF PROFIT, LOSS OF USE, SAVINGS OR REVENUE, OR THE CLAIMS OF + * THIRD PARTIES, WHETHER OR NOT SILICON GRAPHICS, INC. HAS BEEN + * ADVISED OF THE POSSIBILITY OF SUCH LOSS, HOWEVER CAUSED AND ON + * ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE + * POSSESSION, USE OR PERFORMANCE OF THIS SOFTWARE. + * + * US Government Users Restricted Rights + * Use, duplication, or disclosure by the Government is subject to + * restrictions set forth in FAR 52.227.19(c)(2) or subparagraph + * (c)(1)(ii) of the Rights in Technical Data and Computer Software + * clause at DFARS 252.227-7013 and/or in similar or successor + * clauses in the FAR or the DOD or NASA FAR Supplement. + * Unpublished-- rights reserved under the copyright laws of the + * United States. Contractor/manufacturer is Silicon Graphics, + * Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94039-7311. + * + * OpenGL(TM) is a trademark of Silicon Graphics, Inc. + */
Signature · 1 line
1.7.9.5
Quoted 28 lines · Diego
In data martedì 11 giugno 2013 15:10:42, Flanagan, Elizabeth ha scritto:
Quoted 27 lines · Diego
Quoted 5 lines
Hi everybody,
I have written a recipe which I'd like to contribute for glmark2:
https://launchpad.net/glmark2Quoted 7 lines
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#L
icenses 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"
Quoted 8 lines
Quoted 1 line
That should get you what you want.
Hi Elizabeth,
I'm trying to integrate glmark2 into openembedded (meta-oe layer). I know this is not the right mailing list for that task, but I'm still on the license problem.
Ah, ok. In that case, ignore what I just said and patch oe-core's files/common-licenses with the SGI license and files/conf/licenses.conf with:
SPDXLICENSEMAP[SGIv1] = "SGI-1"SRC_DISTRIBUTE_LICENSES += "SGI-1"
That's the right way to do this, IMHO
Quoted 8 lines
I've tried to do as you suggested, but I'm getting:
WARNING: glmark2: No generic license file exists for: SGI-1 in any provider Paul suggested:
LICENSE = "GPLv3+ & SGI-1"
I've tried also:
LICENSE = "GPLv3+ & SGIv1"
but I'm still getting the same error message (obviously with "SGIv1" instead).
Quoted 4 lines
I'm attaching the full patch for you to review if I'm doing something wrong.
Thank you for any hint you might give me,
Diego
-b
Signature · 3 lines
Elizabeth Flanagan Yocto Project Build and Release
In data mercoledì 12 giugno 2013 14:17:05, Flanagan, Elizabeth ha scritto:
Quoted 39 lines · Diego
Quoted 30 lines
In data martedì 11 giugno 2013 15:10:42, Flanagan, Elizabeth ha scritto:
Quoted 29 lines · Diego
Quoted 5 lines
Hi everybody,
I have written a recipe which I'd like to contribute for glmark2:
https://launchpad.net/glmark2Quoted 9 lines
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_Grou
p#L
icenses 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"Quoted 7 lines
Quoted 1 line
That should get you what you want.
Hi Elizabeth,
I'm trying to integrate glmark2 into openembedded (meta-oe layer). I know this is not the right mailing list for that task, but I'm still on the license problem.
Quoted 9 lines
Ah, ok. In that case, ignore what I just said and patch oe-core's files/common-licenses with the SGI license and
files/conf/licenses.confwith:SPDXLICENSEMAP[SGIv1] = "SGI-1"
SRC_DISTRIBUTE_LICENSES+= "SGI-1"That's the right way to do this, IMHO
Hi Elizabeth,
I've tried posting the patch here:
https://lists.yoctoproject.org/pipermail/poky/2013-June/009008.html
But I did not receive a reply. Maybe I did something wrong? Should the patch go to poky ml or to [email protected] ?
Thanks,
Diego
Hi Diego,
Quoted 10 lines · On Tuesday 11 June 2013 14:28:09 Diego wrote:
I have written a recipe which I'd like to contribute for glmark2:
https://launchpad.net/glmark2The 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#Lic
enses Is there any way to deal with that license? What should I put in the LICENSE field in my recipe?
Beth has covered the part about adding the license text, the only remaining piece is how you should set LICENSE within your recipe; assuming you would call this SGI license SGI-1 based on what you said above you would set LICENSE as follows:
LICENSE = "GPLv3+ & SGI-1"
("&" means different licences apply to different parts of the software).
Note also that the LIC_FILES_CHKSUM variable should be set to point to both COPYING and COPYING.SGI.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre