public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Mike Stump <mrs@apple.com>
Cc: Nathanael Nerode <neroden@twcny.rr.com>, gcc@gcc.gnu.org
Subject: Re: doxygen, GPL incompatibility of FDL, and the horror
Date: Tue, 27 May 2003 19:48:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.53.0305272037100.10312@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <6E4E85F2-9079-11D7-8138-003065A77310@apple.com>

On Tue, 27 May 2003, Mike Stump wrote:

> Docs are generated from GPL source.  We want the generated docs to be 
> covered by some other copyright.
> 
> Solution, have the FSF officially bless this and then document it as a 
> blessed transformation.

There may also be a use for having some cases of the converse blessed in
future: GFDL manual used as source for generated code (keeping the
specification of options the compiler accepts, and the --help output, in
magic comments in the manual alongside the full documentation, to minimise
the number of places to be changed to add an option and force
documentation to be added when options are added).  But the requirements
of source in the GPL mean that either the magic comments themselves or the
whole relevant manual files would need to have GPL dual licensing; it
wouldn't be enough for only a generated non-source file to be under the
GPL.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

      parent reply	other threads:[~2003-05-27 19:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25  2:55 Nathanael Nerode
2003-05-25  8:18 ` Gerald Pfeifer
2003-05-27 19:36 ` Mike Stump
2003-05-27 19:40   ` Joe Buck
2003-05-27 19:48   ` Joseph S. Myers [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=Pine.LNX.4.53.0305272037100.10312@kern.srcf.societies.cam.ac.uk \
    --to=jsm28@cam.ac.uk \
    --cc=gcc@gcc.gnu.org \
    --cc=mrs@apple.com \
    --cc=neroden@twcny.rr.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).