You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by Henri Yandell <ba...@apache.org> on 2008/01/23 01:58:31 UTC
Re: aclocal / Autoconf Generated files
For the record Hiram, what did you end up doing here?
On Nov 7, 2006 7:44 AM, Hiram Chirino <hi...@hiramchirino.com> wrote:
> Howdy folks.. aclocal generates a file with the copyright header shown
> bellow. Do I have to include any of those bits in our LICENSE or
> NOTICE files???
>
> # generated automatically by aclocal 1.10 -*- Autoconf -*-
>
> # Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
> # 2005, 2006 Free Software Foundation, Inc.
> # This file is free software; the Free Software Foundation
> # gives unlimited permission to copy and/or distribute it,
> # with or without modifications, as long as this notice is preserved.
>
> # This program is distributed in the hope that it will be useful,
> # but WITHOUT ANY WARRANTY, to the extent permitted by law; without
> # even the implied warranty of MERCHANTABILITY or FITNESS FOR A
> # PARTICULAR PURPOSE.
>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only. Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF. See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: aclocal / Autoconf Generated files
Posted by Henri Yandell <ba...@apache.org>.
On Feb 7, 2008 3:51 PM, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
> Jennifer O'Neill wrote:
> > GNU offers some interesting guidance on this issue. The current
> > Autoconf manual states that there aren't any licensing restrictions
> > *now* on the configuration scripts that Autoconf produces, but under
> > Autoconf v.1, they were covered under the GPL. (See Section 19.1,
> > http://www.gnu.org/software/autoconf/manual/autoconf.html). Of course,
> > the manual isn't dispositive, but this direction doesn't seem consistent
> > with the copyright header if that script was generated by v.1.
>
> With respect to autoconf 2.x... the generate configure is;
>
> Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
> 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
> This configure script is free software; the Free Software Foundation
> gives unlimited permission to copy, distribute and modify it.
>
> It has a dependency, config.sub, and libtool adds ltmain.sh, which
> are GPL, with a specific exception...
>
> # As a special exception to the GNU General Public License, if you
> # distribute this file as part of a program that contains a
> # configuration script generated by Autoconf, you may include it under
> # the same distribution terms that you use for the rest of that program.
>
> which is why it is no problem. It might be good to label the NOTICE
> for source (as opposed to binaries) with the copyright notice for
> additional clarity, but the license itself hovers between an unlimited
> license for use, and the AL, or whatever other license would apply.
Yup, that's the one I was thinking of.
Seems fine for us to use.
Hen
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: aclocal / Autoconf Generated files
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Jennifer O'Neill wrote:
> GNU offers some interesting guidance on this issue. The current
> Autoconf manual states that there aren't any licensing restrictions
> *now* on the configuration scripts that Autoconf produces, but under
> Autoconf v.1, they were covered under the GPL. (See Section 19.1,
> http://www.gnu.org/software/autoconf/manual/autoconf.html). Of course,
> the manual isn't dispositive, but this direction doesn't seem consistent
> with the copyright header if that script was generated by v.1.
With respect to autoconf 2.x... the generate configure is;
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
This configure script is free software; the Free Software Foundation
gives unlimited permission to copy, distribute and modify it.
It has a dependency, config.sub, and libtool adds ltmain.sh, which
are GPL, with a specific exception...
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that program.
which is why it is no problem. It might be good to label the NOTICE
for source (as opposed to binaries) with the copyright notice for
additional clarity, but the license itself hovers between an unlimited
license for use, and the AL, or whatever other license would apply.
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: aclocal / Autoconf Generated files
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
On Feb 7, 2008, at 2:24 PM, Jennifer O'Neill wrote:
> GNU offers some interesting guidance on this issue. The current
> Autoconf manual states that there aren't any licensing restrictions
> *now* on the configuration scripts that Autoconf produces, but
> under Autoconf v.1, they were covered under the GPL. (See Section
> 19.1, http://www.gnu.org/software/autoconf/manual/autoconf.html).
> Of course, the manual isn't dispositive, but this direction doesn't
> seem consistent with the copyright header if that script was
> generated by v.1.
The copyright header includes a license for unlimited redistribution.
The last time I looked, Autoconf specifically permitted the inclusion
of any autoconf-created files (and templates) under whatever license
you choose if the product makes use of autoconf for builds. That is
why we can use it for httpd.
To answer the original question, the copyright header does not need
to appear in LICENSE because those files are all self-contained,
self-described files that only occur as source code in distributions.
See the recent clarifications from SFLC if you want a legal opinion
on such files from the FSF.
....Roy
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: aclocal / Autoconf Generated files
Posted by Jennifer O'Neill <je...@gmail.com>.
GNU offers some interesting guidance on this issue. The current Autoconf
manual states that there aren't any licensing restrictions *now* on the
configuration scripts that Autoconf produces, but under Autoconf v.1, they
were covered under the GPL. (See Section 19.1,
http://www.gnu.org/software/autoconf/manual/autoconf.html). Of course, the
manual isn't dispositive, but this direction doesn't seem consistent with
the copyright header if that script was generated by v.1.
Cheers,
Jennifer
On 2/6/08, Garrett Rooney <ro...@electricjellyfish.net> wrote:
>
> On Feb 6, 2008 9:08 PM, Henri Yandell <ba...@apache.org> wrote:
>
> > This is the bit where one file is 'anyone do anything', and the others
> > are 'GPL, unless the one file is there, in which case they are anyone
> > do anything'?
> >
> > I seem to recall Configure being the important file?
>
> I don't recall the details, but IIRC the end result was that the
> generated configure scripts can be distributed for pretty much any
> purpose (i.e. they've got a header just like the one Hiram posted).
>
> -garrett
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only. Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF. See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
Re: aclocal / Autoconf Generated files
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Feb 6, 2008 9:08 PM, Henri Yandell <ba...@apache.org> wrote:
> This is the bit where one file is 'anyone do anything', and the others
> are 'GPL, unless the one file is there, in which case they are anyone
> do anything'?
>
> I seem to recall Configure being the important file?
I don't recall the details, but IIRC the end result was that the
generated configure scripts can be distributed for pretty much any
purpose (i.e. they've got a header just like the one Hiram posted).
-garrett
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: aclocal / Autoconf Generated files
Posted by Henri Yandell <ba...@apache.org>.
---------- Forwarded message ----------
From: Henri Yandell <ba...@apache.org>
Date: Feb 6, 2008 6:08 PM
Subject: Re: aclocal / Autoconf Generated files
To: Garrett Rooney <ro...@electricjellyfish.net>
On Feb 6, 2008 2:17 PM, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> On Feb 6, 2008 5:04 PM, Henri Yandell <ba...@apache.org> wrote:
> > What does HTTP Server do here?
>
> It ships a similar generated configure script. The license is
> extremely permissive, other than the fact that you have to leave the
> copyright notice you can do whatever you want with those files IIRC,
> so I don't see any reason not to ship them. I don't think they're
> mentioned in LICENSE or NOTICE, but considering how incredibly
> permissively licensed they are I really don't see it mattering one way
> or the other. The license doesn't require notice, and it's far more
> permissive than even the Apache license. Practically every C based
> project on the planet ships with an autotools generated configure
> script or something similar.
This is the bit where one file is 'anyone do anything', and the others
are 'GPL, unless the one file is there, in which case they are anyone
do anything'?
I seem to recall Configure being the important file?
Hen
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: aclocal / Autoconf Generated files
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On Feb 6, 2008 5:04 PM, Henri Yandell <ba...@apache.org> wrote:
> What does HTTP Server do here?
It ships a similar generated configure script. The license is
extremely permissive, other than the fact that you have to leave the
copyright notice you can do whatever you want with those files IIRC,
so I don't see any reason not to ship them. I don't think they're
mentioned in LICENSE or NOTICE, but considering how incredibly
permissively licensed they are I really don't see it mattering one way
or the other. The license doesn't require notice, and it's far more
permissive than even the Apache license. Practically every C based
project on the planet ships with an autotools generated configure
script or something similar.
-garrett
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: aclocal / Autoconf Generated files
Posted by Henri Yandell <ba...@apache.org>.
What does HTTP Server do here?
Hen
On Feb 6, 2008 10:33 AM, Hiram Chirino <hi...@hiramchirino.com> wrote:
> We don't include the aclocal generated files in our source
> distributions. This forces users to have the auto(conf|make) tools
> installed in their system to build the sources but it avoids us having
> to include the generated files.
>
> If we could get clarification clarification on this this issue, and we
> are allowed to ship the generated files, then this would make the
> build process much easier for our users since the dependency list
> would be reduced.
>
> Regards,
> Hiram
>
>
> On Jan 22, 2008 7:58 PM, Henri Yandell <ba...@apache.org> wrote:
> > For the record Hiram, what did you end up doing here?
> >
> >
> > On Nov 7, 2006 7:44 AM, Hiram Chirino <hi...@hiramchirino.com> wrote:
> > > Howdy folks.. aclocal generates a file with the copyright header shown
> > > bellow. Do I have to include any of those bits in our LICENSE or
> > > NOTICE files???
> > >
> > > # generated automatically by aclocal 1.10 -*- Autoconf -*-
> > >
> > > # Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
> > > # 2005, 2006 Free Software Foundation, Inc.
> > > # This file is free software; the Free Software Foundation
> > > # gives unlimited permission to copy and/or distribute it,
> > > # with or without modifications, as long as this notice is preserved.
> > >
> > > # This program is distributed in the hope that it will be useful,
> > > # but WITHOUT ANY WARRANTY, to the extent permitted by law; without
> > > # even the implied warranty of MERCHANTABILITY or FITNESS FOR A
> > > # PARTICULAR PURPOSE.
> > >
> > >
> > >
> > > --
> > > Regards,
> > > Hiram
> > >
> > > Blog: http://hiramchirino.com
> > >
> > > ---------------------------------------------------------------------
> > > DISCLAIMER: Discussions on this list are informational and educational
> > > only. Statements made on this list are not privileged, do not
> > > constitute legal advice, and do not necessarily reflect the opinions
> > > and policies of the ASF. See <http://www.apache.org/licenses/> for
> > > official ASF policies and documents.
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> > > For additional commands, e-mail: legal-discuss-help@apache.org
> > >
> > >
> >
>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
> Open Source SOA
> http://open.iona.com
>
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org