2010/10/11 Maupin, Chase <chase.mau...@ti.com>: > >> -----Original Message----- >> From: openembedded-devel-boun...@lists.openembedded.org >> [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of >> Frans Meulenbroeks >> Sent: Monday, October 11, 2010 12:41 PM >> To: openembedded-devel@lists.openembedded.org >> Subject: Re: [oe] [PATCHv2] recipe licenses: update recipe LICENSE fields >> >> 2010/10/11 Chase Maupin <chasemaupi...@gmail.com>: >> > * While verifying the licensing for the packages I am building >> > into my file system I found that for some packages the >> > LICENSE value set in the recipe was either incorrect or >> > generic and not detailed enough. This patch is my attempt >> > to update the LICENSE fields for these packages to match >> > the actual versions of the licenses in the sources. >> > >> >> [...] >> >> > -LICENSE = "GPLv2" >> > +LICENSE = "GPLv2+" >> >> Doe we want this? >> I think most GPLv2 code carries the clause: >> >> "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 >> of the License, or (at your option) any later version." >> >> Yet currently virtually all of these have GPL or GPLv2 as LICENSE > > Frans, > > My original version of this patch was just changing GPL to GPLv2 for example. > But I was asked about whether it should be GPLv2+ which I guess is more > indicative of the "or later" clause. Does anyone have good guidance here on > how to denote things that are GPLv2 only for now (like git which Linux has a > note in the COPYING file about it being GPLv2) and things that are GPLv2 or > later version? I'm trying for consistency here but I guess there doesn't > seem to be a set policy for how the LICENSE field should be set. >
I have no personal preference, but was just noting the difference. How do others feel about thi? BTW: please don't take this personal. I really appreciate you doing this, but I also am very aware that it is a boring and non-rewarrding job, so we should better aim at getting it right te first time. Frans _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
