From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#23776: Perl's .pod files include timestamps, making Perl package builds non-deterministic Date: Sat, 30 Jul 2016 11:28:15 +0200 Message-ID: <87popvwk40.fsf@gnu.org> References: <87fusdgyg5.fsf@gnu.org> <20160616153927.GB2245@jasmine> <20160619173154.GA26953@jasmine> <20160625182305.GA24122@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37956) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bTQZu-0004y1-7k for bug-guix@gnu.org; Sat, 30 Jul 2016 05:29:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bTQZq-0008PG-36 for bug-guix@gnu.org; Sat, 30 Jul 2016 05:29:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:53883) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bTQZp-0008PC-Vt for bug-guix@gnu.org; Sat, 30 Jul 2016 05:29:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bTQZp-00075P-SQ for bug-guix@gnu.org; Sat, 30 Jul 2016 05:29:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20160625182305.GA24122@jasmine> (Leo Famulari's message of "Sat, 25 Jun 2016 14:23:05 -0400") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Leo Famulari Cc: 23776@debbugs.gnu.org Leo Famulari 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=E2=80=99ll have to update at so= me point, so what about doing that in core-updates-next? Thanks, Ludo=E2=80=99.