Paul Eggert wrote:
Gary V. Vaughan [EMAIL PROTECTED] writes:
Now for the note to the FSF that explains why we need it... here
is a first cut to get the ball rolling:
That looks fine to me. Thanks.
Okay, there have been no corrections or objections in the last 24 hours...
Where do we send it?
Hello,
On Fri, Nov 12, 2004 at 10:25:32AM +, Gary V. Vaughan wrote:
Where do we send it? Direct to rms?
I'd say assign or copyright-clerk are better (at gnu.org, of course).
Stepan
___
Libtool mailing list
[EMAIL PROTECTED]
Now for the note to the FSF that explains why we need it... here
is a first cut to get the ball rolling:
Autoconf, Automake and Libtool have long distributed m4 macro
files that are needed to generate the familiar configure script.
In the spirit of giving our users all the same rights that we
On Wed, 2004-11-10 at 14:57 -0800, Paul Eggert wrote:
As a special exception to the GNU General Public License, if you
distribute this file as part of a package that automatically derives
from this file a configuration script (and perhaps some associated
intermediate files), then you may
Scott James Remnant wrote:
On Wed, 2004-11-10 at 14:57 -0800, Paul Eggert wrote:
As a special exception to the GNU General Public License, if you
distribute this file as part of a package that automatically derives
from this file a configuration script (and perhaps some associated
Gary V. Vaughan [EMAIL PROTECTED] writes:
Now for the note to the FSF that explains why we need it... here
is a first cut to get the ball rolling:
That looks fine to me. Thanks.
___
Libtool mailing list
[EMAIL PROTECTED]
Paul == Paul Eggert [EMAIL PROTECTED] writes:
[...]
Paul Would you use the exact same wording in #2 that you
Paul already uses in the aux scripts? Does that wording still
Paul apply?
I think so. Another idea would be to use a bison-like exception
just to match the license of aclocal.m4:
Alexandre Duret-Lutz wrote:
Paul == Paul Eggert [EMAIL PROTECTED] writes:
[...]
Paul Would you use the exact same wording in #2 that you
Paul already uses in the aux scripts? Does that wording still
Paul apply?
I think so. Another idea would be to use a bison-like exception
just to match the
On second thoughts, why not take this opportunity to unify the license
exception between libtool and automake so we can share code more easily?
Gary V. Vaughan wrote:
Alexandre Duret-Lutz wrote:
Paul == Paul Eggert [EMAIL PROTECTED] writes:
[...]
Paul Would you use the exact same wording in #2
Gary V. Vaughan [EMAIL PROTECTED] writes:
However, even though our intentions are good, and we are merely
clarifying the existing spirit of the exception clauses we have used
all along, is it okay to just edit the license of existing files without
explicit permission from the authors?
It's a
Paul Eggert wrote:
Gary V. Vaughan [EMAIL PROTECTED] writes:
However, even though our intentions are good, and we are merely
clarifying the existing spirit of the exception clauses we have used
all along, is it okay to just edit the license of existing files without
explicit permission from the
Gary V. Vaughan [EMAIL PROTECTED] writes:
Was anybody unhappy with the exception wording in my last post in the
thread? If not we can start from there.
I worry that it's too generous, because it means that if the package
uses the .m4 file as input to autoconf, then the package can also use
Paul == Paul Eggert [EMAIL PROTECTED] writes:
[...]
Paul As a special exception to the GNU General Public License, if you
Paul distribute this file as part of a package that uses the file as input
Paul to GNU Autoconf, GNU Automake, or GNU Libtool, then you may distribute
Paul the resulting
Alexandre Duret-Lutz wrote:
Paul == Paul Eggert [EMAIL PROTECTED] writes:
[...]
Paul As a special exception to the GNU General Public License, if you
Paul distribute this file as part of a package that uses the file as input
Paul to GNU Autoconf, GNU Automake, or GNU Libtool, then you may
Gary == Gary V Vaughan [EMAIL PROTECTED] writes:
Gary Alexandre Duret-Lutz wrote:
[...]
I don't understand the intent of as input to GNU Autoconf, GNU
Automake, or GNU Libtool. AFAICT Libtool does not input m4
files, only the Autoconf tools and aclocal do.
Gary Just trying to cover all
Alexandre Duret-Lutz wrote:
Gary == Gary V Vaughan [EMAIL PROTECTED] writes:
Gary The use of GNU Autoconf is to prevent someone creating their
Gary own tool and calling that Autoconf to circumvent the license.
I don't have a problem with GNU Autoconf, only GNU Libtool :)
(And to some extent with
Alexandre Duret-Lutz [EMAIL PROTECTED] writes:
or any derived output is a lame attempt to allow tools such as
aclocal (without singling out aclocal) to preprocess the file,
as long as the intent is to build a configure script.
I like the idea, but how about if we generalize it to allow
any
Paul == Paul Eggert [EMAIL PROTECTED] writes:
[...]
Paul As a special exception to the GNU General Public License,
Paul if you distribute this file as part of a package that
Paul automatically derives from this file a configuration
Paul script (and perhaps some associated intermediate
Hello!
There is no exception from the GPL in m4/ltoptions.m4, like
there is in the other lt*.m4 files in that directory. Is
that an oversight or is this file only needed for backwards
compatibility or something like that?
Cheers,
Peter
___
Libtool
Hi Ralf,
Ralf Wildenhues wrote:
Hi Peter,
* Peter Ekberg wrote on Tue, Nov 09, 2004 at 01:33:29PM CET:
Hello!
There is no exception from the GPL in m4/ltoptions.m4, like
there is in the other lt*.m4 files in that directory. Is
that an oversight or is this file only needed for backwards
Gary == Gary V Vaughan [EMAIL PROTECTED] writes:
Gary Hi Ralf,
Gary Ralf Wildenhues wrote:
Hi Peter,
* Peter Ekberg wrote on Tue, Nov 09, 2004 at 01:33:29PM CET:
Hello!
There is no exception from the GPL in m4/ltoptions.m4, like
there is in the other lt*.m4 files in that
Alexandre Duret-Lutz [EMAIL PROTECTED] writes:
Some ideas:
1. prefix all the m4/*.m4 licenses with `##' so aclocal
omit them from aclocal.m4 (leaving only the unlimited
permission to ... license added by aclocal)
2. add an exception to all the m4/*.m4 files similar to
I never paid attention to the wording before (they did make sense in
ltdl.c) but the wording of the special exception is not as wonderful
as it should be:
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
#
23 matches
Mail list logo
