From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Could we include diff and grep (etc.) executables on Windows?
Date: Sun, 17 Nov 2019 18:49:46 +0100 [thread overview]
Message-ID: <877e3yz939.fsf@telefonica.net> (raw)
In-Reply-To: 83d0dq5t09.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> Maybe streamlining the MSYS way to install Emacs is the easiest/best way
>> to solve this problem?
>
> Depends on what you mean by that (and what you mean when you say
> "MSYS"). In general, quite a few useful programs don't have native
> Windows ports in MSYS2 repository, so you will get MSYS ports instead,
> and that will cause subtle problems, similar to what happens when one
> mixes Cygwin programs with a native w32 Emacs.
For the case of diff and grep MSYS2 has native binaries, but I agree
with you in general, although it is perfectly ok to run Emacs without
the MSYS2 binaries in sight.
The real problem is that the MSYS2 approach would add some order of
magnitude to the complexity of packaging and publishing Emacs, so there
is no gain over "simply" adding the bare binaries to the current
packages, quite the contrary.
next prev parent reply other threads:[~2019-11-17 17:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 11:50 Could we include diff and grep (etc.) executables on Windows? Mathias Dahl
2019-11-17 16:07 ` Eli Zaretskii
2019-11-17 16:53 ` Stefan Monnier
2019-11-17 17:09 ` Eli Zaretskii
2019-11-17 17:49 ` Óscar Fuentes [this message]
2019-11-17 19:39 ` Stefan Monnier
2019-11-18 15:53 ` Phillip Lord
2019-11-18 18:05 ` Stephen Leake
2019-11-19 14:56 ` Phillip Lord
2019-11-19 15:43 ` Eli Zaretskii
2019-11-19 20:32 ` Óscar Fuentes
2019-11-20 16:11 ` Eli Zaretskii
2019-11-18 15:49 ` Phillip Lord
2019-11-18 16:08 ` Eli Zaretskii
2019-11-18 15:48 ` Phillip Lord
2019-11-18 16:09 ` Eli Zaretskii
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=877e3yz939.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).