all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: timestamp in "no autoloads" section of generated loaddefs.el
Date: Mon, 29 Jun 2015 20:35:13 -0400	[thread overview]
Message-ID: <4f7fqmnida.fsf@fencepost.gnu.org> (raw)


The timestamp in the "files with no autoloads" section of a generated
loaddefs.el file is set to the time that the output was generated.
This is a nuisance for reproducible builds, because it obviously means
that the output file is never the same twice, even if the inputs are.

What do you think about changing that timestamp to "most recent
modification time of any of the files with no autoloads"?

This should cause no change in the time needed to generate the output
when the inputs haven't changed (the mod times are already checked
for every input file). It will cause the maximum possible change in time
when creating the loaddefs.el file from scratch. In testing, I could not
measure any difference in generation time for lisp/loaddefs.el.

That takes care of the reproducibility issue for files like
lisp/net/tramp-loaddefs.el and others.

For lisp/loaddefs.el, the file will still differ between successive
bootstraps of identical inputs, due to varying timestamps on generated
.el files. What do you think about skipping such files altogether when
scanning files for lisp/loaddefs.el? We know they will never contain
autoloads. We already skip such files in other place (via
custom-dependencies-no-scan-regexp and finder-no-scan-regexp).



             reply	other threads:[~2015-06-30  0:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  0:35 Glenn Morris [this message]
2015-06-30 13:55 ` timestamp in "no autoloads" section of generated loaddefs.el Stefan Monnier

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=4f7fqmnida.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.