unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Compressing the Lisp and Info files in the MS-Windows installation
Date: Mon, 15 Apr 2013 18:26:11 +0300	[thread overview]
Message-ID: <83txn76cj0.fsf@gnu.org> (raw)

If the 'gzip' program is available, the Posix installation procedure
("make install") by default compresses all the *.el files in the lisp/
directory and its subdirectories of the installation tree, and also
compresses all the *info files in the info/ directory there.  Are
there any reasons not to do the same when Emacs is installed on
MS-Windows?

A related issue is whether the precompiled Windows binaries should be
distributed with these files compressed.  If they are compressed, end
users will need to have 'gzip' installed to be able to use them.

A compressed tree is 47 MB leaner than an uncompressed one (143 MB vs
190 MB).

I assume that people who prepare the binary distributions for Windows
will run something like "make install prefix=x:/foo/bar", and then
produce a zip file from the tree created at x:/foo/bar.  Thus the
above question is related both to local installations and preparing a
binary distribution for uploading to the FTP site.

(Even if the default is to compress, one can install without
compressing by saying "make install GZIP_PROG=".  So the question
really is what should be the default.)

Comments and opinions are welcome.



             reply	other threads:[~2013-04-15 15:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 15:26 Eli Zaretskii [this message]
2013-04-15 20:02 ` Compressing the Lisp and Info files in the MS-Windows installation Stefan Monnier
2013-04-15 20:13   ` Drew Adams
2013-04-16  8:55     ` Eli Zaretskii
2013-04-16 13:23       ` Drew Adams
2013-05-08 13:02       ` Steinar Bang
2013-04-16  8:50   ` Eli Zaretskii
2013-04-16 13:10     ` Stefan Monnier
2013-04-16 14:33       ` Eli Zaretskii
2013-04-16  8:18 ` Stephen J. Turnbull
2013-04-16  9:10   ` 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=83txn76cj0.fsf@gnu.org \
    --to=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 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).