bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gnulib] Re: licenses again


From: Simon Josefsson
Subject: [Bug-gnulib] Re: licenses again
Date: Thu, 23 Sep 2004 15:50:54 +0200
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux)

address@hidden (Karl Berry) writes:

>     The copy in gnulib/lib/ CVS says GPL.  Can we re-import the LGPL
>     version from glibc?  
>
> But it's intentional that the gnulib copies are GPL.  (It was Paul's
> suggestion.)  We go to some trouble (in srclist-update) to make that
> happen.  We don't just want to LGPL them.  They should be dual-licensed,
> if a change is made.

I'm not sure I understand this.  The LGPL says you can use the work as
GPL if you want.  Is that not enough?

It seems as if the code to replace LGPL with GPL could be moved from
srclist-update to "gnulib-tool --import", if you want to make sure
Texinfo or whatever include GPL'd copies.

I read the above as suggesting there should be two copies of each file
in gnulib, one under LGPL and one under GPL.  I don't see the point of
that.

I'm also not sure I see the point of making sure the gnulib copy in
Texinfo would say GPL instead of LGPL, if the copy in gnulib is
available under LGPL.  Only to avoid having to distribute COPYING.LIB?

>     Who are the authors of minmax.h?
>
> Isn't it a question for all gnulib files?  Just dealing with the files
> that you happen to need right at this instant doesn't seem good.

I thought the argument might become too theoretical if there are no
concrete examples to consider.

>     Before asking Richard, I think I need to have a concrete question.
>
> The question I see is whether it is ok with him if all gnulib files
> (some of which are originally GPL'd) are dual GPL/LGPL.  minmax.h may be
> an example, but surely it's not the whole issue.
>
> This will require (re)explaining to him what gnulib is, what it's for,
> how it is assembled, etc.

I've asked RMS now; for all of gnulib files.

Thanks,
Simon





reply via email to

[Prev in Thread] Current Thread [Next in Thread]