[oe] oe-core license description practices

[Peter Bigot]

I need a resolution to this question so I can complete the port of an
oe-classic recipe to oe-core.

http://www.openembedded.org/wiki/OpenEmbedded-Core states that the
LICENSE field should be "as correct as possible (e.g. 'GPLv2', not
just 'GPL')".  If the upstream package self-describes as "GPL", is it
necessary that this be refined to a more specific version?  I again
note there are numerous existing recipes that do not provide more than
"GPL".

Depending on the answer, I will resubmit with a license of GPL | HPND
or will attempt to contact the upstream maintainer for clarification.

Thanks.

Peter

On Sat, Dec 31, 2011 at 3:28 PM, Peter Bigot <bigotp at acm.org> wrote:
> On Sat, Dec 31, 2011 at 1:40 PM, Koen Kooi <koen at dominion.thruhere.net> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Op 31-12-11 18:32, Peter A. Bigot schreef:
>>> From: "Peter A. Bigot" <bigotp at acm.org>
>>>
>>
>>> +++ b/meta-oe/recipes-devtools/python/python-mysqldb_1.2.3.bb @@ -0,0
>>> +1,24 @@ +DESCRIPTION = "Python interface to MySQL" +HOMEPAGE =
>>> "http://sourceforge.net/projects/mysql-python/" +SECTION =
>>> "devel/python" +# "GPL or the original license based on Python 1.5.2's
>>> license" +LICENSE = "GPL"
>>
>> That really needs a version specifier for the GPL version.
>
> I agree in theory, but what I quoted is what the author provided in
> the README.  It's characterized as an unqualified "GPL" on SourceForge
> and the Python Package Index.  There is no COPYING file in the
> distribution, hence my use of the README as the license file.  I note
> there are several dozen other recipes in meta-openembedded and
> openembedded-core that have the same unqualified GPL license.
>
> Digging a little more, the only further source of guidance is _mysql.c
> which has the following text in a header comment.  If  we assume the
> other files are the same, I can update LICENSE to be GPLv2+.  The
> alternative appears to be an HPND equivalent; I don't know how to
> represent that, as I can't find any recipes that reference it.
>
> How do you want this resolved?
>
> This program is free software; you can redistribute it and/or modify
> it under the terms of the GNU General Public License as published by
> the Free Software Foundation; either version 2, or (at your option)
> any later version. Alternatively, you may use the original license
> reproduced below.
>
> Copyright 1999 by Comstar.net, Inc., Atlanta, GA, US.
>
>                        All Rights Reserved
>
> Permission to use, copy, modify, and distribute this software and its
> documentation for any purpose and without fee is hereby granted,
> provided that the above copyright notice appear in all copies and that
> both that copyright notice and this permission notice appear in
> supporting documentation, and that the name of Comstar.net, Inc.
> or COMSTAR not be used in advertising or publicity pertaining to
> distribution of the software without specific, written prior permission.
>
> COMSTAR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
> INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO
> EVENT SHALL COMSTAR BE LIABLE FOR ANY SPECIAL, INDIRECT OR
> CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF
> USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
> OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
> PERFORMANCE OF THIS SOFTWARE.
>
>
>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (Darwin)
>> Comment: GPGTools - http://gpgtools.org
>>
>> iEYEARECAAYFAk7/ZTYACgkQMkyGM64RGpFc8wCcCU8ufb4FiToMuk0WYns9eAea
>> +QkAoJd+xMnAHtk/Sf5eG2eoCusm8D/G
>> =maSn
>> -----END PGP SIGNATURE-----
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel at lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel