all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: 64 bit official Windows builds
Date: Fri, 08 Jan 2016 13:09:26 +0200	[thread overview]
Message-ID: <83k2nkpbtl.fsf@gnu.org> (raw)
In-Reply-To: <2133bf08-b977-4c85-bdda-a869e202124a@googlegroups.com> (message from Sam Halliday on Fri, 8 Jan 2016 02:44:26 -0800 (PST))

> Date: Fri, 8 Jan 2016 02:44:26 -0800 (PST)
> From: Sam Halliday <sam.halliday@gmail.com>
> Injection-Date: Fri, 08 Jan 2016 10:44:26 +0000
> 
> On Friday, 8 January 2016 09:12:20 UTC, Eli Zaretskii  wrote:
> > No, this compromise contradicts the GPL.  The sources must be
> > available from the same place as the binaries
> 
> 
> Are you sure about this?

Yes, quite sure.  Other ways are theoretically possible, but they are
all impractical.

> My understanding is that source code is to be provided if it is requested:
> 
>   http://www.gnu.org/licenses/gpl-faq.en.html#WhatDoesWrittenOfferValid

Are you (you personally) really going to provide a service of this
kind?  And request that anyone who receives the binaries will have to
provide the same service as well?  Sounds unlikely.  Actually, sounds
like a lip service to me.  And it still requires you to have the
sources handy, for when someone requests them, because you cannot
control what is available at any given time on other sites.

> I believe a GNU Emacs 64bit Windows download should be self-contained and include all runtime DLLs that are necessary for it to run.

That's fine, and I don't disagree.  You just have to provide the
sources used to compile those DLLs from the same place.  Which
shouldn't be a problem, at least not theoretically, since either you
have built them yourself, or you downloaded the binaries from some
GPL-compatible site, which then must provide the sources they used,
right?

FWIW, I do this for 32-bit builds of all the optional libraries needed
by Emacs, see here:

  https://sourceforge.net/projects/ezwinports/files/?source=navbar

It's possible, and it's practically doable.  It is more work than just
building Emacs, though.



  reply	other threads:[~2016-01-08 11:09 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 23:01 64 bit official Windows builds Sam Halliday
2015-12-25  7:35 ` Eli Zaretskii
2015-12-25 13:35   ` Óscar Fuentes
2015-12-25 14:21     ` Eli Zaretskii
2015-12-25 15:32       ` Random832
2015-12-25 15:52         ` Eli Zaretskii
2016-01-07 22:47       ` Arash Esbati
2016-01-08  9:12         ` Eli Zaretskii
2016-01-08 21:42           ` Arash Esbati
2016-01-09  6:58             ` Eli Zaretskii
     [not found]         ` <mailman.1936.1452244338.843.help-gnu-emacs@gnu.org>
2016-01-08 10:44           ` Sam Halliday
2016-01-08 11:09             ` Eli Zaretskii [this message]
     [not found]       ` <mailman.1913.1452206888.843.help-gnu-emacs@gnu.org>
2016-01-09 13:04         ` Sam Halliday
2016-01-10 21:19           ` Arash Esbati
2016-02-11 21:21   ` Nicolas Petton
2016-02-11 21:35     ` Kaushal Modi
2016-02-11 21:53       ` John Mastro
     [not found] ` <mailman.556.1451028922.843.help-gnu-emacs@gnu.org>
2016-01-07 22:38   ` Sam Halliday
2016-01-07 23:15     ` Rasmus
2016-01-08  9:05     ` Eli Zaretskii
2016-02-08 17:44 ` moocow062
2016-02-08 18:06   ` Eli Zaretskii
2016-02-08 18:29     ` Óscar Fuentes
2016-02-08 19:10       ` Eli Zaretskii
2016-02-11 13:58     ` Stefan Monnier
2016-02-11 20:50       ` Eli Zaretskii
2016-02-11 22:16         ` Óscar Fuentes
2016-02-12  6:55           ` Eli Zaretskii
2016-02-12  7:16             ` Óscar Fuentes
2016-02-12  7:48               ` Eli Zaretskii
2016-02-12  8:16                 ` Óscar Fuentes
2016-02-12  8:51                   ` Eli Zaretskii
2016-02-08 22:13   ` djc
2016-02-08 22:51     ` Óscar Fuentes

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=83k2nkpbtl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.