From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Bloat in the Emacs Windows package
Date: Wed, 17 Apr 2019 18:19:59 +0200 [thread overview]
Message-ID: <87r2a0sixc.fsf@telefonica.net> (raw)
In-Reply-To: jwvr2a021gr.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> 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.
>
> BTW, I seem to remember someone working on an "installer" for Emacs
> on Windows. Does anyone know what came out of that?
IIRC it tanked when (L)GLP-mandated source file distribution came to the
scenary.
Creating an installer is quite easy and others did that on the past.
Providing the sources of the tools and libraries that Emacs depends on
makes the work orders of magnitude more difficult.
next prev parent reply other threads:[~2019-04-17 16:19 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 [this message]
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=87r2a0sixc.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--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).