From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48117@debbugs.gnu.org
Subject: bug#48117: 28.0.50; Update of loaddefs.el during normal build is unreliable
Date: Fri, 30 Apr 2021 11:22:00 -0400 [thread overview]
Message-ID: <2weeer23xj.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <8335v8c7o0.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 30 Apr 2021 14:51:11 +0300")
This issue has been present forever.
There are some comments in the Makefiles about it.
There are several issues, eg:
1) autoload generation is slow.
2) the dependencies of the loaddefs files are unknown to make,
and are basically "all lisp files". (You can't even say "just those
files with autoload statements", because removing a previously existing
autoload statement changes the output.)
3) Traditionally, re-making loaddefs files could make trivial changes
to the output that weren't important (eg ordering of the "no
autoloads" section, timestamping), but would still trigger re-dumping emacs.
Which could then trigger regeneration of the autoloads, and
re-dumping, etc. This may be better nowadays, since there is no
longer timestamp information in the loaddefs files (see autoload-timestamps).
next prev parent reply other threads:[~2021-04-30 15:22 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
2021-05-01 13:00 ` Eli Zaretskii
2021-04-30 15:22 ` Glenn Morris [this message]
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
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=2weeer23xj.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=48117@debbugs.gnu.org \
--cc=eliz@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).