From: Eli Zaretskii <eliz@gnu.org>
To: "Ulrich Müller" <ulm@gentoo.org>
Cc: 15297@debbugs.gnu.org
Subject: bug#15297: 24.3.50; Compression of installed .el files should be configurable
Date: Sat, 07 Sep 2013 10:43:34 +0300 [thread overview]
Message-ID: <83mwnpkrfd.fsf@gnu.org> (raw)
In-Reply-To: <21034.52823.580662.797952@a1i15.kph.uni-mainz.de>
> Date: Sat, 7 Sep 2013 08:57:27 +0200
> From: Ulrich Müller <ulm@gentoo.org>
>
> Currently "make install" compresses the installed .el files depending
> on the availability of the gzip program. In Gentoo we make this
> compression configurable; with modern disk sizes the additional
> disk footprint of 34 MiB is normally not an issue.
>
> Since a long time Gentoo uses the following nasty hack for this:
> <http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-editors/emacs/emacs-24.3-r2.ebuild?revision=1.15&view=markup#l98>
>
> However, it would be much cleaner if the upstream build system
> would allow to disable compression.
What's wrong with
GZIP_PROG='' make install ...
? This way, you don't need to decide up front whether you will or
will not want to compress, you decide at "make install" time.
If you want to disable compression of Lisp files, but leave alone the
compression of Info files, then I think it is much better to introduce
GZIP_LISP in the top-level Makefile.in without adding anything to the
configure script. Again, the advantage is that no decision need be
made at configure time.
next prev parent reply other threads:[~2013-09-07 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 6:57 bug#15297: 24.3.50; Compression of installed .el files should be configurable Ulrich Müller
2013-09-07 7:43 ` Eli Zaretskii [this message]
2013-09-07 8:35 ` Ulrich Müller
2013-09-07 8:50 ` Eli Zaretskii
2013-09-07 9:50 ` Ulrich Müller
2013-09-07 10:04 ` Eli Zaretskii
2013-09-07 10:46 ` Ulrich Müller
2013-09-07 12:27 ` Eli Zaretskii
2013-09-08 23:52 ` Glenn Morris
2013-09-07 17:28 ` Glenn Morris
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=83mwnpkrfd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15297@debbugs.gnu.org \
--cc=ulm@gentoo.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.