From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Angelo Graziosi <angelo.graziosi@alice.it>,
emacs-devel@gnu.org
Subject: Re: Emacs 23.4 Updated Windows Binaries published
Date: Mon, 06 Feb 2012 12:46:13 +0900 [thread overview]
Message-ID: <87haz4zksa.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <CANbX364xsAVZztzVqpqvyuF9eg9eLQWUQBXPmFFETWjpFg-QHQ@mail.gmail.com>
Lennart Borgman writes:
> I have not been following this particular thread, but my
> understanding is that only a link to the relevant sources is needed
> now - if we can guarantee that this works. (This was my
> understanding of a message from RMS quite some time ago. I might
> have misunderstood it, though.)
If you mean that Emacs doesn't need to distribute those sources *with
Emacs*, that is true. If you mean that Emacs docs can point to the
upstream sources, you misunderstand.
> A real problem is however to keep the libraries updated.
This is the problem. If you distribute binaries, you must make the
corresponding sources for the exact version of each distributed binary
available according to the GPL. The message you refer to undoubtedly
was explaining certain corner cases where these sources need not be
delivered in the same packages as the binaries (there are pretty
severe conditions on this, though).
If Emacs makes *zero* changes to the 3rd party sources for its
distribution, then theoretically it would be OK to point to them (but
it doesn't satisfy the GPL!) However, that case is likely to be
fairly rare (I would guess that in most cases the build scripts would
be modified or not yet published security patches applied, etc), and
so practically the GPL's requirement that you distribute the
corresponding source *yourself* is simple and reasonable.
next prev parent reply other threads:[~2012-02-06 3:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 16:34 Emacs 23.4 Updated Windows Binaries published Angelo Graziosi
2012-02-05 16:52 ` Eli Zaretskii
2012-02-05 17:12 ` Angelo Graziosi
2012-02-05 17:23 ` Juanma Barranquero
2012-02-06 5:09 ` Christoph Scholtes
2012-02-05 19:10 ` Lennart Borgman
2012-02-05 20:48 ` Eli Zaretskii
2012-02-05 21:24 ` Lennart Borgman
2012-02-06 4:01 ` Eli Zaretskii
2012-02-06 3:46 ` Stephen J. Turnbull [this message]
2012-02-06 4:15 ` Lennart Borgman
2012-02-06 5:22 ` Stephen J. Turnbull
2012-02-06 5:42 ` Lennart Borgman
2012-02-06 6:26 ` Paul Eggert
2012-02-06 7:12 ` Stephen J. Turnbull
2012-02-06 7:46 ` Stephen J. Turnbull
2012-02-06 13:49 ` Lennart Borgman
2012-02-06 15:46 ` Stephen J. Turnbull
2012-02-06 13:47 ` Lennart Borgman
2012-02-06 15:33 ` Stephen J. Turnbull
2012-02-06 15:53 ` Lennart Borgman
2012-02-06 17:01 ` Stephen J. Turnbull
2012-02-06 21:40 ` Lennart Borgman
2012-02-07 9:53 ` Richard Stallman
2012-02-07 13:31 ` Lennart Borgman
2012-02-07 15:57 ` Paul Eggert
-- strict thread matches above, loose matches on Subject: below --
2012-02-05 1:04 Christoph Scholtes
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=87haz4zksa.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=angelo.graziosi@alice.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.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.
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).