From: Philipp Stephani <p.stephani2@gmail.com>
To: David Bremner <david@tethera.net>, Glenn Morris <rgm@gnu.org>
Cc: 22213@debbugs.gnu.org
Subject: bug#22213: 24.5; please allow specification or elimination of timestamp in autoloads
Date: Sun, 20 Dec 2015 09:33:13 +0000 [thread overview]
Message-ID: <CAArVCkQfpyp+yVQ4K5A+q93o=dCmMPrFgDzMN0zfGXn8Xwbdug@mail.gmail.com> (raw)
In-Reply-To: <874mfeusl9.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
David Bremner <david@tethera.net> schrieb am Sa., 19. Dez. 2015 um
20:50 Uhr:
> >
> > So long as the timestamps of your inputs are fixed, the output should
> > not vary. I would be interested to hear if this solves the problem for
> you.
>
> It changes the problem to one of managing timestamps of files. This is
> probably easier than the current situation, but not completely trivial,
> since e.g. both git checkout and build systems that copy files will
> modify timestamps.
>
Agreed, this basically means that you have to do a 'find -exec touch -d @0
'{}' +' or so before every build. That's doable, but increases complexity
and can be brittle if e.g. the filesystem doesn't have accurate mtimes or
something else modifies the input files. Preferably builds should only
depend on relative file names and file contents, not other kinds of
metadata.
[-- Attachment #2: Type: text/html, Size: 1178 bytes --]
next prev parent reply other threads:[~2015-12-20 9:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 18:52 bug#22213: 24.5; please allow specification or elimination of timestamp in autoloads David Bremner
2015-12-19 19:11 ` Glenn Morris
2015-12-19 19:49 ` David Bremner
2015-12-20 3:39 ` Glenn Morris
2015-12-21 0:38 ` Glenn Morris
2015-12-21 1:54 ` Stefan Monnier
2015-12-21 2:20 ` Glenn Morris
2015-12-21 15:59 ` Stefan Monnier
2016-01-07 7:42 ` Glenn Morris
2016-01-08 7:41 ` Stefan Monnier
2016-01-08 14:53 ` Drew Adams
2016-05-25 22:37 ` Glenn Morris
2015-12-21 12:28 ` David Bremner
2015-12-20 9:33 ` Philipp Stephani [this message]
2015-12-20 9:29 ` Philipp Stephani
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='CAArVCkQfpyp+yVQ4K5A+q93o=dCmMPrFgDzMN0zfGXn8Xwbdug@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=22213@debbugs.gnu.org \
--cc=david@tethera.net \
--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 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).