From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 23776@debbugs.gnu.org
Subject: bug#23776: Perl's .pod files include timestamps, making Perl package builds non-deterministic
Date: Sat, 30 Jul 2016 11:28:15 +0200 [thread overview]
Message-ID: <87popvwk40.fsf@gnu.org> (raw)
In-Reply-To: <20160625182305.GA24122@jasmine> (Leo Famulari's message of "Sat, 25 Jun 2016 14:23:05 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Sun, Jun 19, 2016 at 01:31:54PM -0400, Leo Famulari wrote:
>> I noticed that Pod::Man is supposed to respect SOURCE_DATE_EPOCH, as of
>> the upstream module version 4.03 (released 2015-12-06). Does anyone know
>> how to check the version of the module bundled into perl?
>
> In Perl 5.24.0, the integrated podlators module was upgraded from 2.28
> from 4.0.7 [0].
>
> AIUI, changing perl-build-system will require rebuilding all Perl
> packages. If so, how about updating Perl to 5.24.0 instead of changing
> the build system?
>
> Do Perl updates tend to break a lot of Perl packages? If so, changing
> the build system and rebuilding might be done sooner than a Perl update,
> since this change seems unlikely to break any packages.
Sorry for the super late reply. I think we’ll have to update at some
point, so what about doing that in core-updates-next?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-07-30 9:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 11:33 bug#23776: Perl's .pod files include timestamps, making Perl package builds non-deterministic Ludovic Courtès
2016-06-16 15:39 ` Leo Famulari
2016-06-17 8:11 ` Ludovic Courtès
2016-06-17 18:50 ` Leo Famulari
2016-06-18 20:35 ` Ludovic Courtès
2016-06-19 17:31 ` Leo Famulari
2016-06-25 18:23 ` Leo Famulari
2016-07-30 9:28 ` Ludovic Courtès [this message]
2017-01-11 22:27 ` Ludovic Courtès
2017-01-12 17:24 ` Marius Bakke
2017-01-13 8:02 ` Ludovic Courtès
2017-10-31 15:17 ` Ludovic Courtès
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=87popvwk40.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=23776@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).