Re: License of m4/ltoptions.m4

2004-11-10 Thread Paul Eggert
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 allo

Re: License of m4/ltoptions.m4

2004-11-10 Thread Paul Eggert
"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 u

Re: License of m4/ltoptions.m4

2004-11-10 Thread Paul Eggert
"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?

Re: License of m4/ltoptions.m4

2004-11-10 Thread Alexandre Duret-Lutz
>>> "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 intermedi

Re: License of m4/ltoptions.m4

2004-11-10 Thread Gary V. Vaughan
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

Re: License of m4/ltoptions.m4

2004-11-10 Thread Alexandre Duret-Lutz
>>> "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 try

Re: License of m4/ltoptions.m4

2004-11-10 Thread Gary V. Vaughan
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 ma

Re: License of m4/ltoptions.m4

2004-11-10 Thread Alexandre Duret-Lutz
>>> "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

Re: License of m4/ltoptions.m4

2004-11-10 Thread Bruce Korb
"Gary V. Vaughan" wrote: > Here's another: And another: ``The following specific files are hereby deemed "public domain" and you may use them any way you see fit.'' After all, these things are only useful with the Auto* tools and I do not believe that any of them are state secrets, so why spend

Re: License of m4/ltoptions.m4

2004-11-10 Thread Gary V. Vaughan
Paul Eggert wrote: "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

Re: License of m4/ltoptions.m4

2004-11-10 Thread Gary V. Vaughan
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 th

Re: License of m4/ltoptions.m4

2004-11-10 Thread Gary V. Vaughan
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

Re: License of m4/ltoptions.m4

2004-11-10 Thread Gary V. Vaughan
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 mat

Re: License of m4/ltoptions.m4

2004-11-10 Thread Alexandre Duret-Lutz
>>> "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 aclo