From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, 48117@debbugs.gnu.org
Subject: bug#48117: 28.0.50; Update of loaddefs.el during normal build is unreliable
Date: Sat, 01 May 2021 12:29:12 +0000 [thread overview]
Message-ID: <4edb143526f99ac92176@heytings.org> (raw)
In-Reply-To: <837dkiajbd.fsf@gnu.org>
>>> Your proposal would produce marginally better results for a
>>> significantly longer build time, so I don't think it's a net win.
>>
>> If ldefs-boot.el is updated, say, once a week, this would force the
>> regeneration of the loaddefs files at most once a week. Wouldn't that
>> be a reasonable compromise?
>
> Compromise between which alternatives?
>
I see at least the following possible alternatives:
- the current situation, which you describe in your original post, in
which the loaddefs files need to be regenerated manually (inconvenient)
- regenerating the loaddefs files for each make invocation (inefficient)
- copying the ldefs-boot.el onto loaddefs.el when it is more recent (which
IIUC could lose local additions to loaddefs.el)
- automatically regenerating the loaddefs files when ldefs-boot.el is more
recent than loaddefs.el (which I understand could be a bit slow)
- issue only a warning when make is invoked and ldefs-boot.el is more
recent than loaddefs.el (and perhaps add a autoloads or loaddefs target to
the main Makefile)
next prev parent reply other threads:[~2021-05-01 12:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 11:51 bug#48117: 28.0.50; Update of loaddefs.el during normal build is unreliable Eli Zaretskii
2021-04-30 15:01 ` Gregory Heytings
2021-04-30 15:03 ` Eli Zaretskii
2021-04-30 15:47 ` Gregory Heytings
2021-04-30 16:00 ` Eli Zaretskii
2021-04-30 17:32 ` Gregory Heytings
2021-04-30 18:57 ` Eli Zaretskii
2021-04-30 19:08 ` Gregory Heytings
2021-04-30 19:10 ` Eli Zaretskii
2021-04-30 19:20 ` Gregory Heytings
2021-05-01 0:16 ` Glenn Morris
2021-05-01 8:09 ` Gregory Heytings
2021-05-01 8:25 ` Eli Zaretskii
2021-05-01 9:20 ` Gregory Heytings
2021-05-01 9:34 ` Eli Zaretskii
2021-05-01 12:29 ` Gregory Heytings [this message]
2021-05-01 13:00 ` Eli Zaretskii
2021-04-30 15:22 ` Glenn Morris
2021-04-30 15:38 ` Glenn Morris
2021-04-30 15:51 ` Eli Zaretskii
2021-04-30 15:59 ` Andreas Schwab
2021-04-30 16:03 ` Eli Zaretskii
2021-04-30 16:21 ` Andreas Schwab
2021-04-30 17:54 ` Eli Zaretskii
2021-04-30 17:10 ` Glenn Morris
2021-04-30 17:25 ` Glenn Morris
2021-04-30 17:58 ` Eli Zaretskii
2021-05-02 16:59 ` Glenn Morris
2021-05-02 18:54 ` Eli Zaretskii
2021-05-03 8:41 ` Gregory Heytings
2021-04-30 15:48 ` Eli Zaretskii
2021-05-02 7:28 ` Lars Ingebrigtsen
2021-05-02 7:41 ` Eli Zaretskii
2021-12-08 0:36 ` Stefan Kangas
2021-12-08 0:40 ` Lars Ingebrigtsen
2021-12-08 3:32 ` Eli Zaretskii
2022-06-05 16:25 ` Lars Ingebrigtsen
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=4edb143526f99ac92176@heytings.org \
--to=gregory@heytings.org \
--cc=48117@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rgm@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.