From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/3] emacs: Handle compiled and compressed autoloads.
Date: Wed, 09 Dec 2015 11:53:32 +0300 [thread overview]
Message-ID: <87r3iwngtv.fsf@gmail.com> (raw)
In-Reply-To: <87poyhsw3q.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 08 Dec 2015 00:00:09 +0100")
Ludovic Courtès (2015-12-08 02:00 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> * emacs/guix-emacs.el (guix-emacs-autoloads-regexp): New variable.
>> (guix-emacs-find-autoloads-in-directory): Return a list of autoloads
>> without extensions.
>
> LGTM.
>
> However, note that autoloads may only be compressed when we know they do
> not embed store file names (which I think is usually the case.)
Thanks for the info, currently none of the emacs packages provides a
compressed 'autoloads' file.
> Otherwise there’s a risk of fooling the GC, as in
> <http://bugs.gnu.org/20765>.
Hm, OK. I don't fully understand the issue though. So *.el files of
'emacs-w3m-1.4.538+0.20141022' will be compressed, and some of these
*.el.gz files contain store file names. Do these files fool GC?
If so, I think 'emacs-w3m' should be configured with
'--without-compress-install', right?
--
Alex
next prev parent reply other threads:[~2015-12-09 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 10:39 [PATCH 0/3] Update 'emacs-w3m' and improve loading emacs autoloads Alex Kost
2015-12-06 10:39 ` [PATCH 1/3] emacs: Handle compiled and compressed autoloads Alex Kost
2015-12-07 23:00 ` Ludovic Courtès
2015-12-09 8:53 ` Alex Kost [this message]
2015-12-09 13:58 ` Ludovic Courtès
2015-12-10 10:26 ` Alex Kost
2015-12-11 9:51 ` Ludovic Courtès
2015-12-11 11:42 ` Alex Kost
2015-12-06 10:39 ` [PATCH 2/3] gnu: emacs-w3m: Use 'modify-syntax' Alex Kost
2015-12-07 23:00 ` Ludovic Courtès
2015-12-06 10:39 ` [PATCH 3/3] gnu: emacs-w3m: Update to 1.4.538+0.20141022 Alex Kost
2015-12-07 23:00 ` Ludovic Courtès
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=87r3iwngtv.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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/guix.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.