Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfa] License clarification for observer.texi
Date: Tue, 09 May 2006 19:03:00 -0000	[thread overview]
Message-ID: <20060509190346.GA12535@nevyn.them.org> (raw)
In-Reply-To: <ud5en9ght.fsf@gnu.org>

On Tue, May 09, 2006 at 09:53:50PM +0300, Eli Zaretskii wrote:
> > Date: Tue, 9 May 2006 00:05:45 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > > > I am not permitted to include GFDL documentation in the main
> > > > tarball, but I must include observers.texi, in order to build GDB.
> > > 
> > > Why can't you simply include the generated observers.h in the main
> > > tarball?  It has the right license.
> > 
> > Because that would, in my opinion, violate at least the spirit of the
> > GPL.  "Preferred source for modification" is not that file, but the
> > manual.
> 
> I don't see how it would violate the spirit of the GPL.  That spirit
> is, in a nutshell, to let users have full freedom to modify the
> program.  By distributing observers.h you don't hamper that freedom in
> any way.

Different part of the freedom.  Section 3:

===

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

The source code for a work means the preferred form of the work for
making modifications to it.  For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.

===

observers.h is not "source code" according to this definition; we
_require_ contributors to modify observers.texi, so that new observers
are documented, therefore it is not the preferred form. Distributing
the header without distributiong observers.texi would violate this
paragraph.  I think that's what it says, anyway.

Maybe this is "letter" rather than "spirit".

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-05-09 19:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08 21:04 Daniel Jacobowitz
2006-05-08 21:24 ` Eli Zaretskii
2006-05-08 22:18   ` Daniel Jacobowitz
2006-05-09  3:32     ` Eli Zaretskii
2006-05-09  4:06       ` Daniel Jacobowitz
2006-05-09 18:57         ` Eli Zaretskii
2006-05-09 19:03           ` Daniel Jacobowitz [this message]
2006-05-09 19:29             ` Eli Zaretskii
2006-05-09 19:35               ` Daniel Jacobowitz
2006-05-09 12:59       ` Daniel Jacobowitz
2006-05-09 19:20         ` Eli Zaretskii
2006-05-09 19:27           ` Daniel Jacobowitz
2006-05-09 20:29             ` Eli Zaretskii
2006-05-09 20:34               ` Daniel Jacobowitz
2006-05-10  3:23                 ` Eli Zaretskii
2006-05-10  3:52                   ` Daniel Jacobowitz
2006-05-10 17:43                     ` Eli Zaretskii
2006-05-09 20:50               ` Daniel Jacobowitz
2006-05-10 14:59 ` Daniel Jacobowitz
2006-05-10 18:10   ` Eli Zaretskii
2006-05-10 18:49     ` Daniel Jacobowitz

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=20060509190346.GA12535@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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