[OpenAFS-devel] autoconf licensing issues

[Neulinger, Nathan]

From the autoconf docs:

----
Distributing configure Scripts

What are the restrictions on distributing configure
scripts that Autoconf generates?  How does that affect my
programs that use them?

There are no restrictions on how the configuration scripts that Autoconf
produces may be distributed or used. In Autoconf version 1, they were
covered by the GNU General Public License. We still encourage software
authors to distribute their work under terms like those of the GPL, but
doing so is not required to use Autoconf.

Of the other files that might be used with configure, `config.h.in' is under
whatever copyright you use for your `configure.ac'. `config.sub' and
`config.guess' have an exception to the GPL when they are used with an
Autoconf-generated configure script, which permits you to distribute them
under the same terms as the rest of your package. `install-sh' is from the X
Consortium and is not copyrighted.
----

-- Nathan

> -----Original Message-----
> From: Neulinger, Nathan [mailto:nneul@umr.edu]
> Sent: Friday, June 08, 2001 2:49 PM
> To: openafs-devel@openafs.org
> Subject: RE: [OpenAFS-devel] autoconf licensing issues
> 
> 
> I'm not positive, but I thought that the autoconf stuff had a 
> licensing
> exception allowing them to be used under other licenses.
> 
> -- Nathan
> 
> > -----Original Message-----
> > From: Derrick J Brashear [mailto:shadow@dementia.org]
> > Sent: Friday, June 08, 2001 2:44 PM
> > To: openafs-devel@openafs.org
> > Subject: [OpenAFS-devel] autoconf licensing issues
> > 
> > 
> > There are some problems with completeing the autoconfization of
> > OpenAFS. One particularly troubling one is licensing. OpenAFS must
> > obviously continue to be distributed under the IBM public
> > license. However, this makes it not possible to distribute 
> some of the
> > ancillary files that typically get distributed with 
> > autoconf'd packages.
> > 
> > Do any of you know of autoconf-ized packages distributed under
> > non-GPL-compatible licenses?
> > 
> > -D
> > 
> > 
> > _______________________________________________
> > OpenAFS-devel mailing list
> > OpenAFS-devel@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-devel
> > 
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>