From: ludo@gnu.org (Ludovic Courtès)
To: "alírio eyng" <alirioeyng@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: fontforge: Build fonts bit-reproducibly.
Date: Fri, 01 Apr 2016 00:05:02 +0200 [thread overview]
Message-ID: <87io029ucx.fsf@gnu.org> (raw)
In-Reply-To: <CALkz57EFUxjZJH3jgNpXmzFr2QCX0rNKxHtScPazd74BJ+uw6g@mail.gmail.com> ("alírio eyng"'s message of "Thu, 24 Mar 2016 06:43:21 +0000")
alírio eyng <alirioeyng@gmail.com> skribis:
>> Perhaps it would be best to honor the ‘SOURCE_DATE_EPOCH’ environment
>> variable¹ instead of always using zero?
>
>> Fontforge users who expect a meaningful timestamp in there
>> would still have it. And the patch could even be submitted upstream
>> eventually.
> actually there are four values, two are about the font source and two
> are about the font executable
> the font executable times are not readable in the gui and by the work
> on debian, they are not readable in the api, so this change only
> low-level things invisible to users
There may be other programs out there that do display the timestamp,
though.
> this don't change dates on font information (because these come from
> font source)
> so i don't see any reason to fiddle with environment variables and
> conversions to integer in c
Well, I think this is debatable, and most likely in this form the change
is not acceptable for upstream.
I committed it anyway because I think it does more good than harm in our
case.
Thank you!
Ludo’.
prev parent reply other threads:[~2016-03-31 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 13:21 [PATCH] gnu: fontforge: Build fonts bit-reproducibly alírio eyng
2016-03-23 22:21 ` Ludovic Courtès
2016-03-24 6:43 ` alírio eyng
2016-03-31 22:05 ` Ludovic Courtès [this message]
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=87io029ucx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alirioeyng@gmail.com \
--cc=guix-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/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).