unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Phillip Lord <phillip.lord@russet.org.uk>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: Could we include diff and grep (etc.) executables on Windows?
Date: Mon, 18 Nov 2019 15:53:39 +0000	[thread overview]
Message-ID: <87pnhp6v0c.fsf@russet.org.uk> (raw)
In-Reply-To: <jwvimniba62.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 17 Nov 2019 14:39:54 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> 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").
>
> God question.  IIUC one of the main problems with bundling tools is
> having to compile them, keep the versions up-to-date, distributing the
> sources, etc....
>
> So what I meant mostly was: don't actually bundle them, but just provide
> some straightforward way to install Emacs+tools where the tools are
> actually fetched from some other place that handles the job of
> compiling, keeping them up-to-date, distributing the sources, ...
>
> I assumed MSYS could be that "other place" but apparently that's not
> the case.  Maybe that doesn't invalidate the underlying idea, tho.


For the current windows downloads I don't actually compile the tools,
just download them (except where source for the current version of a
binary does not exist, which happens rarely but often enough to
irritate).

I don't do anything for "keeping-up-to-date"; in fact, I keep the
dependencies pinnned at an old version for the entire release
cycle. This is obviously both sensible and problematic at the same time.

Phil



  reply	other threads:[~2019-11-18 15:53 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
2019-11-17 19:39       ` Stefan Monnier
2019-11-18 15:53         ` Phillip Lord [this message]
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=87pnhp6v0c.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=ofv@wanadoo.es \
    /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).