From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: 64 bit official Windows builds Date: Sat, 09 Jan 2016 08:58:30 +0200 Message-ID: <83twmnnsrt.fsf@gnu.org> References: <2577057e-98d3-41ce-ade2-1496648b09c3@googlegroups.com> <837fk3m141.fsf@gnu.org> <87bn9evefh.fsf@wanadoo.es> <83r3ialic7.fsf@gnu.org> <8360z4qvtj.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1452322734 20688 80.91.229.3 (9 Jan 2016 06:58:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 9 Jan 2016 06:58:54 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jan 09 07:58:48 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aHnU6-0004zk-Bk for geh-help-gnu-emacs@m.gmane.org; Sat, 09 Jan 2016 07:58:46 +0100 Original-Received: from localhost ([::1]:39325 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHnU5-0006rJ-Op for geh-help-gnu-emacs@m.gmane.org; Sat, 09 Jan 2016 01:58:45 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50022) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHnTv-0006r0-5p for help-gnu-emacs@gnu.org; Sat, 09 Jan 2016 01:58:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aHnTq-0005lU-IU for help-gnu-emacs@gnu.org; Sat, 09 Jan 2016 01:58:35 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:52480) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHnTq-0005lQ-Es for help-gnu-emacs@gnu.org; Sat, 09 Jan 2016 01:58:30 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1908 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aHnTp-0005nm-Rw for help-gnu-emacs@gnu.org; Sat, 09 Jan 2016 01:58:30 -0500 In-reply-to: (message from Arash Esbati on Fri, 08 Jan 2016 22:42:20 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:108672 Archived-At: > From: Arash Esbati > Date: Fri, 08 Jan 2016 22:42:20 +0100 > > My apologies for the unclear sentence. I meant: I build Emacs on my Win > 64bit machine with Msys2/MinGW-w64 and have access to the necessary > DLLs; it would be a pain if I only had bare Emacs binaries and had to > collect all those DLLs myself somehow. It's some work, but I wouldn't describe that as "pain". Depends on how the sites that offer those DLLs are organized and what tools they offer for downloading and installation. > > No, this compromise contradicts the GPL. The sources must be > > available from the same place as the binaries, > > Hmm, I read the FAQ differently: > > --8<---------------cut here---------------start------------->8--- > Can I put the binaries on my Internet server and put the source on a > different Internet site? (#SourceAndBinaryOnDifferentSites) > > Yes. Section 6(d) allows this. However, you must provide clear > instructions people can follow to obtain the source, and you must > take care to make sure that the source remains available for as long > as you distribute the object code. > > http://www.gnu.org/licenses/gpl-faq.en.html#SourceAndBinaryOnDifferentSites > --8<---------------cut here---------------end--------------->8--- > > I admit that the "you must take care to make sure that the source > remains available for as long as you distribute the object code." part > makes things more complicated, but still ... Not just "complicated", practically impossible. You have no control on what another site holds, and for how long. They could decide to upload a "fixed" archive, which no longer builds for that version of Emacs, or is no longer compatible to it. > > because otherwise it isn't practical for the user who wants to rebuild > > a DLL (e.g., to fix a bug in it or add a feature) of the exact version > > used to build Emacs. (If she tries to do that with a different > > version, that version might be incompatible with the specific version > > of Emacs she uses.) For the same reason, the source distribution > > found near the binary should be of the exact same version used to > > produce the binary, and include any changes done by whoever built the > > binary. > > True, from a developer point of view. But not required by GPL if I get > it correctly. The GPL gives users and developers the same rights. A user who cannot by herself change the program can hire someone who can. That someone will be a developer who will need the exact sources you used. > Please, don't get me wrong here, I do understand your point. But from a > user point of view, I think Emacs becomes more attractive on Windows > if it is provided as a self-contained binary package. I agree. I'm just saying that providing such a self-contained binary means more work on the part of the person who provides that. I know that, because that's what I do when I upload packages to the ezwinports site -- each binary zip contains all of its dependency DLLs, and there's always a source zip for each of those dependencies, in the same directory, or sometimes in the sibling directory. That's what the GPL requires.