From: Mark Wielaard <mark@klomp.org>
To: Jonas Maebe <jonas.maebe@elis.ugent.be>
Cc: Jim Ingham <jingham@apple.com>, gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 7.0 release process created
Date: Tue, 22 Sep 2009 14:31:00 -0000 [thread overview]
Message-ID: <1253629868.20668.42.camel@springer.wildebeest.org> (raw)
In-Reply-To: <92D837F2-68E5-45E8-AB54-F133E7DB2CCA@elis.ugent.be>
On Tue, 2009-09-22 at 15:29 +0200, Jonas Maebe wrote:
> On 22 Sep 2009, at 14:58, Mark Wielaard wrote:
>
> > If the gdb binary as conveyed to the user depends on being
> > codesigned by
> > a particular authorization key, then that should be part of the
> > corresponding source code that the user receives. So then the signing
> > authorization keys would be available for any rebuild gdb binary that
> > the user creates.
>
> Isn't that only as of GPLv3 and later? (the whole "Installation
> Information" discussion) Apple's gdb is based on an old (GPLv2) fork.
You would have to aks FSF legal for details of whether not offering part
of the corresponding source code is allowed under GPLv2 vs GPLv3. But it
seems obvious to me that if you cannot build a functionally equivalent
working binary from the sources as provided, then you are not in
compliance of offering the complete source code of the executable work.
So I would assume the requirement to provide it to the user is
equivalent under both versions. The GPLv3 text just makes it a bit more
explicit that this is the intent it seems.
Cheers,
Mark
next prev parent reply other threads:[~2009-09-22 14:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 22:20 Joel Brobecker
2009-09-18 0:42 ` Tom Tromey
2009-09-18 0:49 ` Hui Zhu
2009-09-20 2:54 ` Jack Howarth
2009-09-20 3:50 ` Paul Pluzhnikov
2009-09-20 14:32 ` Joel Brobecker
2009-09-20 15:02 ` Paul Pluzhnikov
2009-09-20 15:28 ` Joel Brobecker
2009-09-20 16:14 ` Paul Pluzhnikov
2009-09-20 17:12 ` Joel Brobecker
2009-09-20 17:36 ` Jack Howarth
2009-09-20 17:40 ` Joel Brobecker
2009-09-20 18:37 ` Paul Pluzhnikov
2009-09-20 19:12 ` Jack Howarth
2009-09-20 20:22 ` Paul Pluzhnikov
2009-09-21 4:34 ` Joel Brobecker
2009-09-21 12:57 ` Jack Howarth
2009-09-21 13:36 ` Jonas Maebe
2009-09-21 13:46 ` Jack Howarth
2009-09-21 13:55 ` Jonas Maebe
2009-09-21 19:19 ` Jim Ingham
2009-09-22 12:59 ` Mark Wielaard
2009-09-22 13:30 ` Jonas Maebe
2009-09-22 14:31 ` Mark Wielaard [this message]
2009-09-22 15:56 ` Daniel Jacobowitz
2009-09-22 17:10 ` Jack Howarth
2009-09-22 17:34 ` Daniel Jacobowitz
2009-09-22 18:11 ` Mark Wielaard
2009-09-22 19:28 ` Tom Tromey
2009-09-21 13:26 ` Jack Howarth
2009-09-20 16:19 ` Paul Pluzhnikov
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=1253629868.20668.42.camel@springer.wildebeest.org \
--to=mark@klomp.org \
--cc=gdb@sourceware.org \
--cc=jingham@apple.com \
--cc=jonas.maebe@elis.ugent.be \
/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