Skip Menu |

This queue is for tickets about the ExtUtils-MakeMaker CPAN distribution.

Report information
The Basics
Id: 121713
Status: open
Priority: 0/
Queue: ExtUtils-MakeMaker
People
Owner: Nobody in particular
Requestors: hugo.vandersanden [...] pirum.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Tue May 16 11:08:24 2017 hugo.vandersanden [...] pirum.com - Ticket created
CC: "hv [...] crypt.org" <hv [...] crypt.org>
Subject: pure_install dependencies
Date: Tue, 16 May 2017 11:34:47 +0000
To: "bug-ExtUtils-MakeMaker [...] rt.cpan.org" <bug-ExtUtils-MakeMaker [...] rt.cpan.org>
From: "Hugo van der Sanden, Pirum" <hugo.vandersanden [...] pirum.com>
For reasons [1], I can't run manifypods on a variety of MakeMaker-built CPAN modules, but I should be able to build, test and install fine without the pods. The MM-generated Makefiles usefully provide targets 'pure_all' and 'pure_install' for (presumably) just this sort of purpose; unfortunately the pure_install targets specify 'all' as a dependency, which tries to run manifypods again. I think the intention was that the pure_install targets depend on 'pure_all' instead. Hugo [1] Building in a Linux machine in a VM on a Windows box - it can't run manifypods, cos ':' is illegal in filenames on the underlying filesystem.
  Tue May 16 14:54:30 2017 HVDS [...] cpan.org - Correspondence added
RT-Send-CC: hugo.vandersanden [...] pirum.com
A bit later I found there's an additional problem for the (rarer) dist with subdirs: 'make all' is invoked in subdirs regardless of the target in the parent, I think it should rather invoke the same target as was invoked in the parent. I hit that in Proc::ProcessTable, the only one of a dozen-odd dists I built today in that environment. Please let me know if you'd prefer a separate ticket filed for this. Hugo
  Tue May 16 14:54:31 2017 The RT System itself - Status changed from 'new' to 'open'
  Fri Apr 13 10:12:50 2018 fawaka [...] gmail.com - Correspondence added
Subject: Re: [rt.cpan.org #121713] pure_install dependencies
Date: Fri, 13 Apr 2018 16:12:19 +0200
To: bug-ExtUtils-MakeMaker [...] rt.cpan.org
From: Leon Timmermans <fawaka [...] gmail.com>
On Tue, May 16, 2017 at 5:08 PM, Hugo van der Sanden, Pirum via RT < bug-ExtUtils-MakeMaker@rt.cpan.org> wrote: Show quoted text
> Tue May 16 11:08:24 2017: Request 121713 was acted upon. > Transaction: Ticket created by hugo.vandersanden@pirum.com > Queue: ExtUtils-MakeMaker > Subject: pure_install dependencies > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: hugo.vandersanden@pirum.com > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=121713 > > > > For reasons [1], I can't run manifypods on a variety of MakeMaker-built > CPAN modules, but I should be able to build, test and install fine without > the pods. > > The MM-generated Makefiles usefully provide targets 'pure_all' and > 'pure_install' for (presumably) just this sort of purpose; unfortunately > the pure_install targets specify 'all' as a dependency, which tries to run > manifypods again. > > I think the intention was that the pure_install targets depend on > 'pure_all' instead. >
It seems the word pure is overloaded here. pure_install means only whole files are written, no files (in particular, perllocal.pod) are written to; whereas pure_all means everything needed for tests (thus not including man pages). The two are unrelated. Show quoted text
> [1] Building in a Linux machine in a VM on a Windows box - it can't run > manifypods, cos ':' is illegal in filenames on the underlying filesystem. >
That does sound like a legitimate problem deserving a solution. Leon