all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 23776@debbugs.gnu.org
Subject: bug#23776: Perl's .pod files include timestamps, making Perl package builds non-deterministic
Date: Sat, 25 Jun 2016 14:23:05 -0400	[thread overview]
Message-ID: <20160625182305.GA24122@jasmine> (raw)
In-Reply-To: <20160619173154.GA26953@jasmine>

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.

Your advice requested :)

[0]
https://metacpan.org/pod/distribution/perl/pod/perldelta.pod#Updated-Modules-and-Pragmata

  reply	other threads:[~2016-06-25 18:24 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 [this message]
2016-07-30  9:28       ` Ludovic Courtès
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160625182305.GA24122@jasmine \
    --to=leo@famulari.name \
    --cc=23776@debbugs.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 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.