unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: sources and scripts for generated files
Date: Mon, 26 May 2014 11:43:28 +0200	[thread overview]
Message-ID: <87k39850zj.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87tx8c99m4.fsf@uwakimon.sk.tsukuba.ac.jp

"Stephen J. Turnbull" <stephen@xemacs.org> writes:

> Andreas Röhler writes:
>
>  > assume you are kidding.
>
> No, he's not.  GPL "sources" are defined as the preferred form for
> editing if you wish to make changes to the software.  If the .h file
> is as easy to edit as the other, it might be the preferred form for
> local changes (or at least acceptable).  On the other hand, it's
> converted by an automatic process *and* the script that does so is
> part of Emacs (AIUI).  So there's a strong presumption that the file
> from ICU is the source.
>
>  > If not kidding, I'm still wondering, resp. asking: please make the
>  > GPL a text every Emacs core developer may understand without
>  > undergoing expensive law-studies.
>
> That cannot be done; the GPL's primary purpose is to protect various
> interests in the covered Work, and readability to non-lawyers takes a
> back seat to that.
>
> But this part is not hard to understand.
>
> (1) You must provide sources that are reasonably convenient to edit.

No, the preferred form for modification.  If there is an upstream
document from which the sources are generated _and_ this upstream
document is not one-of-its-kind (meaning that there will never be
updated documents in the same format), then obviously the upstream is
the preferred form for modifications.  Because then rerunning the
harvesting script is a proper part of maintenance, and then changes to
the generated document would get overwritten.

-- 
David Kastrup




  reply	other threads:[~2014-05-26  9:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  2:31 sources and scripts for generated files Glenn Morris
2014-05-26  5:33 ` Jan Djärv
2014-05-26  8:32   ` Andreas Röhler
2014-05-26  9:10     ` Jan D.
2014-05-26  9:23     ` Stephen J. Turnbull
2014-05-26  9:43       ` David Kastrup [this message]
2014-05-26 11:35       ` Andreas Röhler
2014-05-26 14:06         ` Stephen J. Turnbull
2014-05-26 15:56 ` Paul Eggert
2014-05-26 18:02 ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k39850zj.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).