From: Richard Copley <rcopley@gmail.com>
To: Phillip Lord <phillip.lord@russet.org.uk>
Cc: Eli Zaretskii <eliz@gnu.org>, Kevin Layer <layer@known.net>,
Emacs Development <emacs-devel@gnu.org>
Subject: Re: Are there non-mingw32 binaries for Windows?
Date: Mon, 21 Nov 2016 00:18:35 +0000 [thread overview]
Message-ID: <CAPM58ohsvC+WfJoyZgxpSg6u7wuYsyh+rEgSMHi6agvMjHfZVg@mail.gmail.com> (raw)
In-Reply-To: <87y40d6e0f.fsf@russet.org.uk>
On 20 November 2016 at 21:24, Phillip Lord <phillip.lord@russet.org.uk> wrote:
> Richard Copley <rcopley@gmail.com> writes:
>> Without wishing to confuse matters, there /is/ an Emacs that's
>> "native to MSYS" and uses MSYS-style mounts, but it's a different
>> beast. The MSYS package repository has three builds:
>>
>> mingw32/mingw-w64-i686-emacs 25.1-1
>> mingw64/mingw-w64-x86_64-emacs 25.1-1
>> msys/emacs 25.1-1
>>
>> The first two are native (to Windows) and are hardly patched from
>> upstream. They're very similar to the official FSF builds for Windows.
>> The third is "native to MSYS". Most people don't need it but it can
>> come in handy if you spend time in MSYS.
>
>
> I think for 25.2 I should change the name of the zip files on
> ftp.gnu.org. The "mingw-w64" addition is not really necessary and might
> well cause confusion.
OK, but to clarify, the three names I quoted above are the package
names on MSYS2, and all the packages there are prefixed in the same
way. But that's according to some schema that's operative for them --
no reason to cargo-cult it into Emacs.
But is it worth looking into whether there's a more-or-less
established convention that could be said to apply to the binaries
available on ftp.gnu.org?
next prev parent reply other threads:[~2016-11-21 0:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 23:47 Are there non-mingw32 binaries for Windows? Kevin Layer
2016-11-17 1:08 ` Óscar Fuentes
2016-11-17 3:38 ` Eli Zaretskii
2016-11-17 7:16 ` Fabrice Popineau
2016-11-17 14:58 ` Phillip Lord
2016-11-17 17:54 ` Kevin Layer
2016-11-17 19:36 ` Óscar Fuentes
2016-11-17 20:41 ` Eli Zaretskii
2016-11-17 21:46 ` Kevin Layer
2016-11-18 19:28 ` Richard Copley
2016-11-20 21:24 ` Phillip Lord
2016-11-21 0:18 ` Richard Copley [this message]
2016-11-21 20:56 ` Phillip Lord
2016-11-20 21:21 ` Phillip Lord
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=CAPM58ohsvC+WfJoyZgxpSg6u7wuYsyh+rEgSMHi6agvMjHfZVg@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=layer@known.net \
--cc=phillip.lord@russet.org.uk \
/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).