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 04:06:00 -0000	[thread overview]
Message-ID: <20060509040545.GA26150@nevyn.them.org> (raw)
In-Reply-To: <umzdran51.fsf@gnu.org>

On Tue, May 09, 2006 at 06:32:42AM +0300, Eli Zaretskii wrote:
> > Date: Mon, 8 May 2006 18:18:35 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb-patches@sourceware.org
> > 
> > Debian no longer permits the distribution of FDL'd works in the "main"
> > distribution.
> 
> Ah, it's _that_ issue.
> 
> > 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.

> Anyway, I'm uneasy about making such a change because of the Debian's
> controversy.  When faced with issues like this (i.e. the same source
> that is used to produce both code and documentation), RMS always said
> that in practice this isn't a problem, since either the produced docs
> or the produced code is of insignificant amount.  So if distributing
> observers.h is somehow not an option, I think we should ask Richard
> for guidance.

I suppose I will have to do that, then.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-05-09  4:06 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 [this message]
2006-05-09 18:57         ` Eli Zaretskii
2006-05-09 19:03           ` Daniel Jacobowitz
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=20060509040545.GA26150@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