all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: "Official" binary of Emacs-24.4 for MS-Windows
Date: Sat, 25 Oct 2014 10:00:23 +0200	[thread overview]
Message-ID: <CAH8Pv0jYO1=mE+33nn01MR96fqTWXuFZeRHd5BJ3F8d1V=FNoQ@mail.gmail.com> (raw)
In-Reply-To: <83d29g64u4.fsf@gnu.org>

> I don't object to not compressing the files, if compressing them
> causes trouble on some systems.

This system is Windows 8.1 64-bit, and, according to what you said:

>> I don't see a reason not to compress files.  Emacs can display and use
>> them just fine, even if gzip.exe is not installed/available, right?

not being able to show the manual (nor visiting .gz files -- I've just
tried) seemed like a bug.  It this expected (when gzip.exe is not
available) or should I report this as a bug?

Regarding the format of the binary archive, there are several options:

  Format  Archive Size
  zip     50 MB
  tar.gz  50 MB
  tar.xz  32 MB
  7z      31 MB

As you see, the last two formats produce an archive considerably
smaller.  Which format should I choose?

Regarding the name of the binary archive, the convention so far has
been "emacs-VERSION-bin-i386".  But if I eval `system-configuration'
from that Emacs I get `i686-pc-mingw32'.  So, perhaps we should name
the archive as "emacs-24.4-bin-i686", or (even better IMO),
"emacs-24.4-bin(i686-pc-mingw32)".  I like the latter format, because
it is a general and compact way of telling not only the hardware
architecture, but also OS flavor it was built for.  It is quite
self-explanatory.

But of course the choice is yours. Which filename should I choose?

And finally, note that I haven't got an answer yet to the request I
sent 2 days ago (to ftp-upload@gnu.org) for ftp upload rights.  So I
still can't upload anything.  (I could send the archive to anyone with
proper upload right...)

-- Dani Moncayo



  reply	other threads:[~2014-10-25  8:00 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 15:13 "Official" binary of Emacs-24.4 for MS-Windows Dani Moncayo
2014-10-24 15:17 ` Windows build pipeline - " Nic Ferrier
2014-10-24 15:42   ` Dani Moncayo
2014-10-24 15:55 ` Eli Zaretskii
2014-10-24 15:56   ` Dani Moncayo
2014-10-24 17:26     ` Eli Zaretskii
2014-10-24 18:03       ` Dani Moncayo
2014-10-24 19:29         ` Eli Zaretskii
2014-10-24 20:21           ` Dani Moncayo
2014-10-25  6:28             ` Eli Zaretskii
2014-10-25  8:00               ` Dani Moncayo [this message]
2014-10-25  8:11                 ` Eli Zaretskii
2014-10-25  8:39                   ` Dani Moncayo
2014-10-25  9:23                     ` Eli Zaretskii
2014-10-25  9:31                       ` Dani Moncayo
2014-10-25  9:37                         ` Eli Zaretskii
2014-10-25 11:08                           ` Dani Moncayo
2014-10-25 11:36                             ` Eli Zaretskii
2014-10-25 13:27                               ` Dani Moncayo
2014-10-30 15:04                                 ` Dani Moncayo
2014-10-30 15:58                                   ` Eli Zaretskii
2014-10-25  8:38                 ` Glenn Morris
2014-10-30 15:06                   ` Dani Moncayo
2014-10-30 15:25                     ` Glenn Morris
2014-11-10  5:34 ` Eli Zaretskii
2014-11-10  7:29   ` Dani Moncayo
2014-11-10  7:34     ` Dani Moncayo
2014-11-10 10:49     ` Eli Zaretskii
2014-11-12 12:02       ` Dani Moncayo
2014-11-12 13:59         ` Thorsten Jolitz
2014-11-12 14:02           ` Dani Moncayo
2014-11-12 15:44             ` Thorsten Jolitz
2014-11-12 17:39           ` Alexander Shukaev
2014-11-13  9:57             ` Thorsten Jolitz
2014-11-15 12:09         ` Dani Moncayo
2014-11-15 13:03           ` Eli Zaretskii
     [not found]           ` <<83egt4fwf4.fsf@gnu.org>
2014-11-15 14:53             ` Drew Adams
2014-11-15 15:31           ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH8Pv0jYO1=mE+33nn01MR96fqTWXuFZeRHd5BJ3F8d1V=FNoQ@mail.gmail.com' \
    --to=dmoncayo@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.