This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Libgfortran licensing
- From: Paul Brook <paul at codesourcery dot com>
- To: gcc at gcc dot gnu dot org
- Cc: Toon Moene <toon at moene dot indiv dot nluug dot nl>,Tobias Schlüter <tobias dot schlueter at physik dot uni-muenchen dot de>,GCC Fortran mailing list <fortran at gcc dot gnu dot org>
- Date: Tue, 31 Aug 2004 23:11:47 +0100
- Subject: Re: Libgfortran licensing
- Organization: CodeSourcery
- References: <4134DDAB.2040406@physik.uni-muenchen.de> <4134F562.5010101@moene.indiv.nluug.nl>
On Tuesday 31 August 2004 23:02, Toon Moene wrote:
> Tobias Schlüter wrote:
> > To make things short: under which license should libgfortran be licensed?
> >
> > While doing some cleanups on libgfortran I noticed that some files are
> > licensed under the plain GPL, others under the LGPL, I didn't see any
> > that say GPL+exception, but there could well be. Could someone who has
> > the authority to make such statements for the FSF please tell me under
> > which license libgfortran should be licensed (I assume that the library
> > should be licensed under the terms of the GPL+exception, as GCC's other
> > runtime libraries).
>
> Stop ! Wait !
>
> Only the original author(s) of these pieces can determine under what
> license they want their contributions distributed. As "we" didn't write
> all of them (some were written by Andy Vaught), we cannot decide
> unilaterally to change the licensing. If the license does not conform
> to the one normally used for run-time library code, and we didn't write
> the specific code ourselves, we should recode the functionality.
Doesn't the copyright assignment give the FSF power licence the code as they
see fit?
IIRC libiberty only had problems changing the licence because the code wasn't
FSF copyright.
Paul