[oe] Question about automake licensing in recipe
Maupin, Chase
chase.maupin at ti.com
Fri Sep 24 13:28:14 UTC 2010
> -----Original Message-----
> From: openembedded-devel-bounces at lists.openembedded.org
> [mailto:openembedded-devel-bounces at lists.openembedded.org] On Behalf Of
> Phil Blundell
> Sent: Friday, September 24, 2010 7:56 AM
> To: openembedded-devel at lists.openembedded.org
> Subject: Re: [oe] Question about automake licensing in recipe
>
> On Fri, 2010-09-24 at 21:38 +0930, Graham Gower wrote:
> > Basically, automake have to contact all their contributors to allow
> > their GPLv2 code to be distributed under GPLv3. Or they have to pull
> > the GPLv3 code out.
>
> If automake has followed the usual GNU conventions then all the
> contributors will have assigned copyright of their code to the FSF
> anyway. In that case, the FSF can (being the copyright holder)
> unilaterally decide what licence it should be distributed under.
As a follow up I'm beginning to wonder if the COPYING file in the lib directory wasn't auto-generated by automake itself. Newer versions of automake will apply the "gnu" strictness by default and will create a COPYING file for GPLv3. Either way, I have submitted an e-mail to the automake list asking for them to clarify their licensing.
>
> If they haven't done that then, yeah, they would probably need the
> permission of the original authors to change the licensing.
>
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
More information about the Openembedded-devel
mailing list