From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: emacs-dev: 'unpack' phase does not seem to preserve timestamps
Date: Wed, 23 May 2018 17:01:09 +0200 [thread overview]
Message-ID: <87h8myxvpm.fsf@gnu.org> (raw)
In-Reply-To: <874lj6iaap.fsf@gmail.com> (Pierre Neidhardt's message of "Thu, 17 May 2018 17:14:38 +0200")
Hello,
Pierre Neidhardt <ambrevar@gmail.com> skribis:
> Since all file timestamps are set to Epoch by 'unpack', the build phase
> tries to rebuild everything.
> And since the files unpacked to "source" are read-only, `make` fails to
> regenerate the files that go in "source".
Yes, that’s annoying, but that’s expected. Perhaps the ‘unpack’
phase could automatically make the copy that it creates with
‘copy-recursively’ writable?
> From the source, 'unpack' is supposed to preserve the timestamp:
>
> (define* (unpack #:key source #:allow-other-keys)
> "Unpack SOURCE in the working directory, and change directory within the
> source. When SOURCE is a directory, copy it in a sub-directory of the current
> working directory."
> (if (file-is-directory? source)
> (begin
> (mkdir "source")
> (chdir "source")
>
> ;; Preserve timestamps (set to the Epoch) on the copied tree so that
> ;; things work deterministically.
> (copy-recursively source "."
> #:keep-mtime? #t)
It does preserve timestamps, but since SOURCE is in the store, its
timestamps are all set to the Epoch.
But that’s OK: Git doesn’t specify timestamps anyway.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-05-23 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 15:14 emacs-dev: 'unpack' phase does not seem to preserve timestamps Pierre Neidhardt
2018-05-23 15:01 ` Ludovic Courtès [this message]
2018-05-23 20:40 ` Pierre Neidhardt
2018-05-24 12:13 ` Ludovic Courtès
2018-05-24 12:29 ` Pierre Neidhardt
2018-05-24 20:33 ` Ludovic Courtès
2018-05-25 12:09 ` Pierre Neidhardt
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=87h8myxvpm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ambrevar@gmail.com \
--cc=help-guix@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/guix.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.