From: Daniel Jacobowitz <drow@false.org>
To: "Volkmann, Patrick" <patrick.volkmann@siemens.com>
Cc: "'gdb@sourceware.org'" <gdb@sourceware.org>
Subject: Re: GDB 6.8 - license terms
Date: Tue, 21 Apr 2009 15:51:00 -0000 [thread overview]
Message-ID: <20090421141153.GA31143@caradoc.them.org> (raw)
In-Reply-To: <DE45E0660ACFF44FAEC72596D57610040E9029126E@DEERLF0CX5.ww004.siemens.net>
On Tue, Apr 21, 2009 at 04:03:46PM +0200, Volkmann, Patrick wrote:
> Hi,
>
> i would appreciate your help with the following issue:
>
> The file "README" in the GDB 6.8 root contains the following phrase (line 42):
> "...See the file COPYING or
> COPYING.LIB in the various directories, for a description of the
> GNU General Public License terms under which you can copy the files..."
>
> Now we detected in the source code GPL v2 and GPL v3 license terms
> (e.g in the root, \gdb-6.8\COPYING and \gdb-6.8\COPYING3)
>
> But some subfolders only contain the GPL v2 license
> (e.g. \gdb-6.8\bfd\COPYING, \gdb-6.8\gdb\COPYING, ... )
>
> Because of the incompatibility between GPLv3 and GPLv2,
> we are not sure if we can consider the whole component as licensed under the terms of GPL v3.
>
> Can you please help me with this issue?
Most FSF-owned code is licensed under the "GPL v2 or later" or "GPL v3
or later". When you mix those two, you must handle the result under
GPL v3 (or a later version as released by the FSF in the future).
It's not the COPYING files that are important, in any case, but the
notices on the individual sources. GDB moved to GPLv3 around
2007-08-23, which was before the release of GDB 6.8.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-04-21 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 14:12 Volkmann, Patrick
2009-04-21 15:51 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090421141153.GA31143@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=patrick.volkmann@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox