From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Set FORCE_SOURCE_DATE=1 by default
Date: Tue, 21 Jun 2022 14:06:22 -0700 [thread overview]
Message-ID: <875yktafqp.fsf@contorta> (raw)
In-Reply-To: <878rppagl4.fsf@contorta>
[-- Attachment #1: Type: text/plain, Size: 2613 bytes --]
On 2022-06-21, Vagrant Cascadian wrote:
> On 2022-06-15, Ludovic Courtès wrote:
>> Vagrant Cascadian <vagrant@reproducible-builds.org> skribis:
>>> From 7a39330b56934accef14b5e2ac003e211c7c6c5b Mon Sep 17 00:00:00 2001
>>> From: Vagrant Cascadian <vagrant@reproducible-builds.org>
>>> Date: Fri, 10 Jun 2022 16:12:59 -0700
>>> Subject: [PATCH] guix: gnu-build-system: Set FORCE_SOURCE_DATE in
>>> set-SOURCE-DATE-EPOCH phase.
>>>
>>> * guix/build/gnu-build-system.scm (set-SOURCE-DATE-EPOCH): Set
>>> FORCE_SOURCE_DATE=1. Update URL.
>>
>> [...]
>>
>>> (define* (set-SOURCE-DATE-EPOCH #:rest _)
>>> - "Set the 'SOURCE_DATE_EPOCH' environment variable. This is used by tools
>>> -that incorporate timestamps as a way to tell them to use a fixed timestamp.
>>> -See https://reproducible-builds.org/specs/source-date-epoch/."
>>> - (setenv "SOURCE_DATE_EPOCH" "1"))
>>> + "Set the 'SOURCE_DATE_EPOCH' and 'FORCE_SOURCE_DATE' environment variables.
>>> +This is used by tools that incorporate timestamps as a way to tell them to use
>>> +a fixed timestamp. See https://reproducible-builds.org/docs/source-date-epoch/."
>>> + (setenv "SOURCE_DATE_EPOCH" "1")
>>> + (setenv "FORCE_SOURCE_DATE" "1"))
>>
>> I’d mention above that FORCE_SOURCE_DATE is honored exclusively by
>> TeX Live.
Still not terribly happy with it, but I think I can cope with this
updated version:
diff --git a/guix/build/gnu-build-system.scm b/guix/build/gnu-build-system.scm
index d84411c090..cbfbd2a209 100644
--- a/guix/build/gnu-build-system.scm
+++ b/guix/build/gnu-build-system.scm
@@ -56,10 +56,14 @@ (define time-monotonic time-tai))
(else #t))
(define* (set-SOURCE-DATE-EPOCH #:rest _)
- "Set the 'SOURCE_DATE_EPOCH' environment variable. This is used by tools
-that incorporate timestamps as a way to tell them to use a fixed timestamp.
-See https://reproducible-builds.org/specs/source-date-epoch/."
- (setenv "SOURCE_DATE_EPOCH" "1"))
+ "Set the 'SOURCE_DATE_EPOCH' and 'FORCE_SOURCE_DATE' environment variables.
+This is used by tools that incorporate timestamps as a way to tell them to use
+a fixed timestamp. Setting 'FORCE_SOURCE_DATE' is needed in order for TeX
+Live to respect 'SOURCE_DATE_EPOCH', which is used to generate documentation
+in various packages. See
+https://reproducible-builds.org/docs/source-date-epoch/."
+ (setenv "SOURCE_DATE_EPOCH" "1")
+ (setenv "FORCE_SOURCE_DATE" "1"))
(define (first-subdirectory directory)
"Return the file name of the first sub-directory of DIRECTORY or false, when
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-06-21 21:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 23:53 Set FORCE_SOURCE_DATE=1 by default Vagrant Cascadian
2022-06-15 8:58 ` Ludovic Courtès
2022-06-15 16:24 ` Vagrant Cascadian
2022-06-21 20:48 ` Vagrant Cascadian
2022-06-21 21:06 ` Vagrant Cascadian [this message]
2022-06-22 3:57 ` Maxim Cournoyer
2022-06-22 6:08 ` Vagrant Cascadian
2022-06-22 13:53 ` Ludovic Courtès
2022-06-22 15:11 ` Vagrant Cascadian
2022-06-22 17:41 ` Maxim Cournoyer
2022-06-22 13:59 ` Maxim Cournoyer
2022-06-23 1:03 ` Vagrant Cascadian
2022-06-23 16:44 ` Maxim Cournoyer
2022-07-03 1:58 ` Vagrant Cascadian
2022-07-04 13:14 ` Ludovic Courtès
2022-08-12 15:32 ` Vagrant Cascadian
2022-06-22 15:16 ` Time namespace for build sandbox (was Re: Set FORCE_SOURCE_DATE=1 by default) Zhu Zihao
2022-06-22 15:35 ` Vagrant Cascadian
2022-06-22 16:41 ` Maxime Devos
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yktafqp.fsf@contorta \
--to=vagrant@reproducible-builds.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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/guix.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).