From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: [PATCH PING] Honor 'SOURCE_DATE_EPOCH' when generating autoloads.
Date: Wed, 23 Dec 2015 16:52:08 +0000 [thread overview]
Message-ID: <CAArVCkSASv=sB=E6ccBC5UAjE=nV1VS12pQUx31ZVgzZMx_Q3g@mail.gmail.com> (raw)
In-Reply-To: <83fuytp1au.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
Eli Zaretskii <eliz@gnu.org> schrieb am Mi., 23. Dez. 2015 um 17:38 Uhr:
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Wed, 23 Dec 2015 16:01:30 +0000
> >
> > OK, here's a patch.
>
> Thanks. A few minor comments.
>
> > +AC_ARG_ENABLE(deterministic-dump,
> > +[AS_HELP_STRING([--enable-deterministic-dump],
> > + [Make dumping deterministic by removing system-specific
> > + information from the dump, such as host names and
> > + timestamps.])])
>
> I'd prefer calling this "deterministic-build", so that we could use it
> to solve any other similar problems unrelated to dumping. Maybe even
> "reproducible-build".
>
I think we have two categories of builds here:
- Builds that get executed when running 'make' in the Emacs directory. This
includes dumping and byte compilation of code bundled with Emacs.
- Builds that get executed by running an initialized Emacs binary, likely
on a different machine. This includes e.g. byte compilation of third-party
libraries.
I think these two categories are separate enough to have two different
variables. This patch only addresses the first category, therefore I didn't
want to use the generic term "build", but "dump" is also not quite right.
Do we have a proper term for the first category? "bootstrap"? "emacs-build"?
>
> (If we do change the option, we should also change the name of the
> variable and the cpp symbol.)
>
> > +(defconst emacs-build-system
> > + (if deterministic-dump "unknown" (system-name))
> > "Name of the system on which Emacs was built.")
>
> Can we find a better string, like "elided" or "undisclosed"?
> "Unknown" sounds too self-derogatory.
>
Sure, 'elided' is fine.
>
> > + DEFVAR_BOOL ("deterministic-dump", Vdeterministic_dump,
> > + doc: /* If t, attempt to make dumping deterministic by avoiding
>
> I think the usual style is "If non-nil".
>
ok
>
> > +sources of nondeterminism such as absolute paths, the hostname, or
>
> GNU coding standards frown on using "path" for anything that isn't
> PATH-style list of directories. Please use "file name" instead.
>
>
ok
[-- Attachment #2: Type: text/html, Size: 3309 bytes --]
next prev parent reply other threads:[~2015-12-23 16:52 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 17:03 [PATCH] Honor 'SOURCE_DATE_EPOCH' when generating autoloads Ludovic Courtès
2015-11-29 10:44 ` [PATCH PING] " Ludovic Courtès
2015-11-29 16:02 ` Eli Zaretskii
2015-11-29 16:57 ` Ludovic Courtès
2015-11-29 18:12 ` Eli Zaretskii
2015-11-29 20:38 ` Ludovic Courtès
2015-11-30 17:00 ` John Wiegley
2015-11-30 19:30 ` Ludovic Courtès
2015-12-07 18:36 ` Philipp Stephani
2015-12-07 18:58 ` Paul Eggert
2015-12-07 19:00 ` Philipp Stephani
2015-12-07 19:14 ` Paul Eggert
2015-12-20 12:48 ` Philipp Stephani
2015-12-20 16:37 ` Eli Zaretskii
2015-12-20 18:39 ` Philipp Stephani
2015-12-20 19:03 ` Eli Zaretskii
2015-12-20 21:27 ` Paul Eggert
2015-12-23 1:13 ` John Wiegley
2015-12-23 16:01 ` Philipp Stephani
2015-12-23 16:39 ` Eli Zaretskii
2015-12-23 16:52 ` Philipp Stephani [this message]
2015-12-23 17:10 ` Eli Zaretskii
2015-12-23 17:38 ` Philipp Stephani
2015-12-23 21:09 ` Paul Eggert
2015-12-24 3:33 ` Eli Zaretskii
2015-12-24 6:54 ` Paul Eggert
2015-12-24 16:18 ` Eli Zaretskii
2015-12-27 9:53 ` Philipp Stephani
2015-12-27 16:10 ` Eli Zaretskii
2016-02-29 21:52 ` Philipp Stephani
2016-03-01 16:36 ` Paul Eggert
2016-03-01 21:46 ` Philipp Stephani
2016-03-02 18:24 ` Paul Eggert
2016-03-02 18:30 ` Philipp Stephani
2016-03-22 13:30 ` Philipp Stephani
2016-03-22 20:37 ` Paul Eggert
2016-03-22 21:46 ` Philipp Stephani
2016-03-22 21:58 ` Paul Eggert
2016-03-23 8:03 ` Andreas Schwab
2016-04-06 21:29 ` Philipp Stephani
2015-12-27 23:26 ` Paul Eggert
2015-12-28 16:26 ` Eli Zaretskii
2015-12-28 18:00 ` Paul Eggert
2015-12-28 18:23 ` Eli Zaretskii
2015-12-29 3:01 ` Paul Eggert
2015-12-29 15:38 ` Eli Zaretskii
2015-12-29 16:47 ` Paul Eggert
2015-12-29 17:59 ` Eli Zaretskii
2015-12-29 20:33 ` Paul Eggert
2015-12-07 23:11 ` Ludovic Courtès
2015-11-30 9:22 ` Alex Kost
2015-11-29 20:22 ` Paul Eggert
2015-11-29 20:42 ` 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
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='CAArVCkSASv=sB=E6ccBC5UAjE=nV1VS12pQUx31ZVgzZMx_Q3g@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).