From: phillip.lord@russet.org.uk (Phillip Lord)
To: "Björn Lindqvist" <bjourne@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Bloat in the Emacs Windows package
Date: Wed, 17 Apr 2019 18:39:49 +0100 [thread overview]
Message-ID: <87mukocyze.fsf@russet.org.uk> (raw)
In-Reply-To: <CALG+76dRyKdfph-M4oRVwJQh2RzvzkjqMdaO4LB-4poyP5tjCA@mail.gmail.com> ("Björn Lindqvist"'s message of "Wed, 17 Apr 2019 17:07:23 +0200")
Björn Lindqvist <bjourne@gmail.com> writes:
>> Some people want the binary zip to include all the optional features
>> that Emacs on Windows can support.
>
> Fair enough. But what optional features are missing from the
> -no-deps.zip file? GnuTLS support in eww?
Image support is the one most people would hit I think. I have no
evidence for this statement of course.
> Maybe the name of the emacs-26.1-x86_64.zip file could be changed to
> indicate that it is an "all inclusive" package?
No, I do not want to do this. I changed this from emacs-25 -> emacs-26
because I think most people would want it all to just work following the
clicking the obvious download link.
> Most users are probably fine with downloading the smaller
> emacs-26.1-x86_64-no-deps.zip instead.
I might be able to get this data from the ftp logs. Not sure how
reliable that is, however.
> I don't think I've ever had Emacs on Windows crash on me. But if it did,
> how would I get hold of the stack trace? Executables on Windows are
> mostly run by clicking on their icons and that hides the standard input
> and output.
>
>> But if Phillip can afford prodicing separate debug info file for
>> Emacs, we could have the cake and eat it, too.
>
> Do you mean afford as in time or as in the Windows build is run on a
> rented server?
My time. I am entirely happy to either not add the debug info, or to put
it in a different file. I know how to do the former not the latter.
>> > It is also
>> > aesthetically displeasing -- hackers like minimalism and hate bloat.
>>
>> FWIW, I think you the first one to complain about this.
>
> Well, yes, but how many Windows users complained about the lack of
> debugging symbols in Emacs 24?
My guess is none. It's why I am glad (and suggested) raising the issue
on Emacs-devel.
>> > And while on the subject of Windows packaging. How come there is no
>> > MSI installer for Emacs? It shouldn't be to hard to put one together
>> > and it would make Emacs a little easier to install for newbies.
>>
>> What tools to use to produce the binary distribution is entirely up to
>> the person who does that. And of course MSI is not free software.
>
> The WiX Toolset which one can use to build MSIs is free software. I
> don't know about the MSI format itself, but it would surprise me if
> there are any legal hurdles since MSIs are supposed to be distributed by
> ISVs.
If you are willing to help develop a MSI for Emacs-27 then that would be
a good thing and, so long as building it can be relatively automated on
top of the current process, then I will be happy to release that for
Emacs-27 onward. This and code signing are the two things that I have
not got working for the Windows build, but would like to.
Phil
next prev parent reply other threads:[~2019-04-17 17:39 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
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 [this message]
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=87mukocyze.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=bjourne@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).