From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Vagrant Cascadian <vagrant@reproducible-builds.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, "Guix Devel" <guix-devel@gnu.org>
Subject: Re: Set FORCE_SOURCE_DATE=1 by default
Date: Wed, 22 Jun 2022 13:41:55 -0400 [thread overview]
Message-ID: <8735fw61ek.fsf@gmail.com> (raw)
In-Reply-To: <87edzgu402.fsf@contorta> (Vagrant Cascadian's message of "Wed, 22 Jun 2022 08:11:57 -0700")
Hi Vagrant,
Vagrant Cascadian <vagrant@reproducible-builds.org> writes:
> On 2022-06-22, Ludovic Courtès wrote:
>> Vagrant Cascadian <vagrant@reproducible-builds.org> skribis:
>>
>>> On 2022-06-21, Maxim Cournoyer wrote:
>>
>> [...]
>>
>>>> I'd much prefer challenging that stance than "endorsing" it in Guix :-).
>>>> I think it'd be OK to reluctantly add it in as a stop-gap fix in Guix,
>>>> but *only* after opening an issue to discuss it upstream and linking to
>>>> that issue in Guix.
>>>
>>> I get it. I really do. It kind of grates at me every time I think about
>>> this.
>>
>> :-)
>>
>> Another option would be to patch TeX Live, assuming the
>> FORCE_SOURCE_DATE bit is well isolated in a single file. Would that
>> seem reasonable/feasible/desirable to you, Vagrant?
>
> Only problem I see is indefinitely maintaining a patch to TeX Live that
> upstream is unlikely to take ... but other than that, this sounds great!
I wouldn't expect this simple substitution should be too difficult to
maintain :-).
> We'd also get a clearer idea of which packages are affected, rather than
> setting it globally and rebuilding everything...
I don't think it's of critical importance; what we care about here is
having the software reproducible, not knowing exactly which esoteric
environment variable enabled it.
> I'll also try to dig up at least one of the threads where there was some
> discussion with upstream... hopefully without getting too caught up in
> that old rabbit hole.
That'd be nice.
Thanks!
Maxim
next prev parent reply other threads:[~2022-06-22 17:42 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735fw61ek.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=vagrant@reproducible-builds.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.