From: phillip.lord@russet.org.uk (Phillip Lord)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Bloat in the Emacs Windows package
Date: Wed, 17 Apr 2019 18:26:36 +0100 [thread overview]
Message-ID: <87v9zcczlf.fsf@russet.org.uk> (raw)
In-Reply-To: <jwvd0lkddim.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 17 Apr 2019 08:39:52 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Some people want the binary zip to include all the optional features that
>> Emacs on Windows can support. This zip includes all of the dependencies for
>> those optional features. Arguably, some of the auxiliary files, like header
>> files and import libraries, could be omitted, but determining which ones are
>> required is a very non-trivial and time-consuming job, so I can understand
>> why Phillip, who volunteered to produce the binary zips, didn't do that.
>> This "one cannot fit all" problem is why we also have the bare-minimum zip
>> with only the dependencies that are absolutely required.
>
> Indeed. But I wonder about licensing issues of some of those binaries:
> for those packages which are (L)GPL'd, do we distribute the
> corresponding source somewhere, like the license requires us to do?
https://ftp.gnu.org/gnu/emacs/windows/emacs-26/emacs-26-deps-mingw-w64-src.zip
Packaged at the same time as the binaries, which is about the best I can
do to keep the source the same as that which was used to produce the
source.
>
>>> addpm.exe 577 kB => 2 282 kB
>>> ctags.exe 956 kB => 3 245 kB
>>> emacs.exe 8 989 kB => 121 740 kB
>>> emacs-24.5.exe 8 989 kB => 121 740 kB (emacs-26.1.exe)
>> Stripping emacs.exe produces a 29MB file for Emacs 26.2.
>
> I wonder what caused the 9MB => 29MB jump between 24.5 and 26?
Probably the -static flag that I added. Otherwise, the 64bit file
required libpthread and (at the time) I had no ability to distribute
this because I didn't have a way of generating the source.
>> We don't provide any shell scripts or batch files because the build on Posix
>> systems doesn't. Once again, it's hard to blame volunteers for using the
>> build products as is, without adding any more work.
>
> FWIW, I think saving a 100MB is worth the extra work.
It isn't extra work. I just change the compile options on my build
scripts. I genuinely have no idea why they are there in the first place;
perhaps I put them in because someone told me to, perhaps not.
> (but, indeed, using hard-links is the better option when available:
> I often just `rm src/emacs-[0-9]*` to get rid of old Emacs releases it'd
> be much trickier to do if src/emacs were a script that runs
> src/emacs-27.0.50.5).
It's also possible to turn on NTFS file compression which will remove
both this and lots of other duplications in the Emacs install. AFAIK,
this is a user option, however, although I might be able to do it with
the installer version for Emacs-27.
Phil
next prev parent reply other threads:[~2019-04-17 17:26 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 5:01 Bloat in the Emacs Windows package Björn Lindqvist
2019-04-17 7:31 ` Eli Zaretskii
2019-04-17 11:15 ` Van L
2019-04-17 11:26 ` Eli Zaretskii
2019-04-17 12:39 ` Stefan Monnier
2019-04-17 14:49 ` Eli Zaretskii
2019-04-17 16:17 ` Eli Zaretskii
2019-04-18 22:02 ` Björn Lindqvist
2019-04-19 7:00 ` Eli Zaretskii
2019-04-17 17:26 ` Phillip Lord [this message]
2019-04-17 17:55 ` Stefan Monnier
2019-04-19 0:02 ` Björn Lindqvist
2019-04-19 7:33 ` Eli Zaretskii
2019-04-19 13:23 ` Óscar Fuentes
2019-04-22 21:04 ` Phillip Lord
2019-04-22 21:41 ` Óscar Fuentes
2019-04-17 13:42 ` Stefan Monnier
2019-04-17 16:19 ` Óscar Fuentes
2019-04-17 17:28 ` Phillip Lord
2019-04-17 15:07 ` Björn Lindqvist
2019-04-17 16:32 ` Eli Zaretskii
2019-04-18 23:44 ` Björn Lindqvist
2019-04-19 7:27 ` Eli Zaretskii
2019-04-19 14:17 ` Óscar Fuentes
2019-04-19 15:05 ` Eli Zaretskii
2019-04-22 20:55 ` Phillip Lord
2019-04-17 17:39 ` Phillip Lord
2019-04-17 18:06 ` Stefan Monnier
2019-04-17 18:32 ` Eli Zaretskii
2019-04-18 16:05 ` Phillip Lord
2019-04-18 19:08 ` Eli Zaretskii
2019-04-18 21:19 ` Phillip Lord
2019-04-18 23:12 ` Óscar Fuentes
2019-04-19 6:29 ` Eli Zaretskii
2019-04-22 20:40 ` Phillip Lord
2019-04-23 2:25 ` Stefan Monnier
2019-04-23 10:01 ` Phillip Lord
2019-04-23 11:28 ` Robert Pluim
2019-04-23 21:49 ` Phillip Lord
2019-04-26 16:30 ` Phillip Lord
2019-04-26 17:04 ` Óscar Fuentes
2019-04-26 21:41 ` Phillip Lord
2019-04-27 18:12 ` Björn Lindqvist
2019-04-27 18:17 ` Phillip Lord
2019-05-03 1:06 ` Björn Lindqvist
2019-05-03 6:49 ` Eli Zaretskii
2019-05-03 18:38 ` Björn Lindqvist
2019-05-03 18:42 ` Eli Zaretskii
2019-05-03 20:20 ` Stefan Monnier
2019-04-23 5:37 ` Eli Zaretskii
2019-04-17 15:44 ` Phillip Lord
2019-04-17 16:25 ` Óscar Fuentes
2019-04-17 16:46 ` Eli Zaretskii
2019-04-18 16:00 ` Phillip Lord
2019-04-18 15:56 ` Phillip Lord
2019-04-18 16:39 ` Ó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
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=87v9zcczlf.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).