From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 27563@debbugs.gnu.org
Subject: bug#27563: [PATCH v3 0/2] Make ghostscript reproducible.
Date: Fri, 07 Jul 2017 19:51:10 +0200 [thread overview]
Message-ID: <87o9swxhip.fsf@gnu.org> (raw)
In-Reply-To: <20170707174422.14e87fc2@scratchpost.org> (Danny Milosavljevic's message of "Fri, 7 Jul 2017 17:44:22 +0200")
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Fri, 07 Jul 2017 17:18:15 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> OK, makes sense. Maybe we can still have it disabled (or enabled) by
>> environment variable
>
> Sure. Any suggestions for the name of the environment variable?
For CreationDate/ModDate, I think it should honor SOURCE_DATE_EPOCH as
in
<https://anonscm.debian.org/git/printing/ghostscript.git/tree/debian/patches/2010_add_build_timestamp_setting.patch?id=e2bf3ad7026afe13636d4937430c3fdae7854078>.
For the two UUIDs (and “ID” too?), maybe we can use, say,
GS_GENERATE_UUIDS; if set to 0 or “no” it’s disable, otherwise it’s
enabled.
> Also, where would we set it so the build processes of all the other
> packages actually pick it up?
Eventually we can add it to gnu-build-system.scm, but for now, given
that core-updates is well built, we should add it on a case-by-case
basis. I don’t think there are that many packages that produce PDFs,
but I could be wrong.
How does that sound?
Thank you,
Ludo’.
next prev parent reply other threads:[~2017-07-07 17:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 18:08 bug#27563: ghostscript-with-cups is not reproducible Danny Milosavljevic
2017-07-03 18:16 ` bug#27563: [PATCH] gnu: ghostscript: Add phase "remove-timestamps" Danny Milosavljevic
2017-07-03 19:18 ` Efraim Flashner
2017-07-05 21:57 ` Ludovic Courtès
2017-07-04 19:08 ` Leo Famulari
2017-07-03 19:46 ` bug#27563: [PATCH v2] gnu: ghostscript: Remove timestamps Danny Milosavljevic
2017-07-06 9:07 ` bug#27563: [PATCH] gnu: ghostscript: Don't write document UUID; use "" as instance UUID Danny Milosavljevic
2017-07-07 11:55 ` Ludovic Courtès
2017-07-07 13:28 ` Danny Milosavljevic
2017-07-06 10:32 ` bug#27563: [PATCH v3 0/2] Make ghostscript reproducible Danny Milosavljevic
2017-07-06 10:32 ` bug#27563: [PATCH v3 1/2] gnu: ghostscript: Don't write document UUID; use "" as instance UUID Danny Milosavljevic
2017-07-06 10:32 ` bug#27563: [PATCH v3 2/2] gnu: ghostscript: Write document ID only when encrypting Danny Milosavljevic
2017-07-07 12:02 ` Ludovic Courtès
2017-07-07 13:21 ` Danny Milosavljevic
2017-07-07 16:21 ` Leo Famulari
2017-07-07 16:42 ` Danny Milosavljevic
2017-07-07 17:24 ` Leo Famulari
2017-07-08 13:50 ` Leo Famulari
2017-07-07 17:45 ` Ludovic Courtès
2017-07-07 12:00 ` bug#27563: [PATCH v3 0/2] Make ghostscript reproducible Ludovic Courtès
2017-07-07 13:25 ` Danny Milosavljevic
2017-07-07 15:18 ` Ludovic Courtès
2017-07-07 15:44 ` Danny Milosavljevic
2017-07-07 17:51 ` Ludovic Courtès [this message]
2017-07-07 18:20 ` Danny Milosavljevic
2017-07-08 14:32 ` Ludovic Courtès
2017-07-09 23:40 ` bug#27563: [PATCH v4 0/3] " Danny Milosavljevic
2017-07-09 23:46 ` bug#27563: [PATCH v4 1/3] gnu: ghostscript: Make "/ID" optional, depending on environment variable Danny Milosavljevic
2017-07-09 23:46 ` bug#27563: [PATCH v4 2/3] gnu: ghostscript: Make XMP UUID headers " Danny Milosavljevic
2017-07-10 15:23 ` Ludovic Courtès
2017-07-09 23:46 ` bug#27563: [PATCH v4 3/3] gnu: ghostscript: Make "/CreationDate", "/ModDate" optoinal, " Danny Milosavljevic
2017-07-10 15:25 ` Ludovic Courtès
2017-07-10 15:21 ` bug#27563: [PATCH v4 1/3] gnu: ghostscript: Make "/ID" optional, " Ludovic Courtès
2017-07-10 16:35 ` bug#27563: [PATCH v4 0/3] Make ghostscript reproducible Danny Milosavljevic
2017-07-07 15:34 ` bug#27563: [PATCH v3 0/2] " Danny Milosavljevic
2017-07-07 17:46 ` Ludovic Courtès
2017-07-06 10:59 ` bug#27563: ghostscript-with-cups is not reproducible Danny Milosavljevic
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=87o9swxhip.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27563@debbugs.gnu.org \
--cc=dannym@scratchpost.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).