From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: 64 bit official Windows builds
Date: Sat, 09 Jan 2016 08:58:30 +0200 [thread overview]
Message-ID: <83twmnnsrt.fsf@gnu.org> (raw)
In-Reply-To: <n6pah8$vf9$1@ger.gmane.org> (message from Arash Esbati on Fri, 08 Jan 2016 22:42:20 +0100)
> From: Arash Esbati <esbati@gmx.de>
> 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.
next prev parent reply other threads:[~2016-01-09 6:58 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 [this message]
[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
[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=83twmnnsrt.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.