Bug #23603 for Carp-Assert: Dependencies, dependencies

Fri Nov 24 17:04:36 2006 ANDK [...] cpan.org - Ticket created

Subject:

Dependencies, dependencies

Whazzat? Is this a known bug? That's an unhealthy tendency that people always believe that this perl is in the PATH. cpan[28]> install Carp::Assert Running install for module 'Carp::Assert' Running make for M/MS/MSCHWERN/Carp-Assert-0.18.tar.gz Is already unwrapped into directory /home/k/.cpan/build/Carp-Assert-0.18-JRZ16H CPAN.pm: Going to build M/MS/MSCHWERN/Carp-Assert-0.18.tar.gz Checking if your kit is complete... Looks good Writing Makefile for Carp::Assert make[1]: Entering directory `/home/k/.cpan/build/Carp-Assert-0.18-JRZ16H' cp lib/Carp/Assert.pm blib/lib/Carp/Assert.pm make[1]: pod2test: Command not found make[1]: *** [testifypods] Error 127 make[1]: Leaving directory `/home/k/.cpan/build/Carp-Assert-0.18-JRZ16H' MSCHWERN/Carp-Assert-0.18.tar.gz /usr/bin/make -- NOT OK Running make test Can't test without successful make Running make install Make had returned bad status, install seems impossible Failed during this command: MSCHWERN/Carp-Assert-0.18.tar.gz : make NO

Sun Dec 03 17:15:17 2006 schwern [...] pobox.com - Correspondence added

Subject:	Re: [rt.cpan.org #23603] Dependencies, dependencies
Date:	Sun, 03 Dec 2006 14:14:49 -0800
To:	bug-Carp-Assert [...] rt.cpan.org
From:	Michael G Schwern <schwern [...] gmail.com>

Andreas Koenig via RT wrote: Show quoted text

> Whazzat? Is this a known bug? That's an unhealthy tendency that people > always believe that this perl is in the PATH. > > cpan[28]> install Carp::Assert > Running install for module 'Carp::Assert' > Running make for M/MS/MSCHWERN/Carp-Assert-0.18.tar.gz > Is already unwrapped into directory > /home/k/.cpan/build/Carp-Assert-0.18-JRZ16H > > CPAN.pm: Going to build M/MS/MSCHWERN/Carp-Assert-0.18.tar.gz > > Checking if your kit is complete... > Looks good > Writing Makefile for Carp::Assert > make[1]: Entering directory `/home/k/.cpan/build/Carp-Assert-0.18-JRZ16H' > cp lib/Carp/Assert.pm blib/lib/Carp/Assert.pm > make[1]: pod2test: Command not found

The assumption here is that because Test::Inline is installed you have pod2test in your PATH (look at MY::top_targets in the Makefile.PL). That assumption appears to be broken in your case. So it can either A) use Test::Inline directly rather than go through an intermediate program or B) check if pod2test is in the PATH.

Sun Dec 03 17:15:20 2006 The RT System itself - Status changed from 'new' to 'open'

Mon Dec 04 01:53:46 2006 andreas.koenig.gmwojprw [...] franz.ak.mind.de - Correspondence added

CC:	ANDK [...] cpan.org
Subject:	Re: [rt.cpan.org #23603] Dependencies, dependencies
Date:	Mon, 04 Dec 2006 07:53:20 +0100
To:	bug-Carp-Assert [...] rt.cpan.org
From:	andreas.koenig.gmwojprw [...] franz.ak.mind.de (Andreas J. Koenig)

Show quoted text

>>>>> On Sun, 03 Dec 2006 17:15:21 -0500, "Michael G Schwern via RT" <bug-Carp-Assert@rt.cpan.org> said:

Show quoted text

> <URL: http://rt.cpan.org/Ticket/Display.html?id=23603 >

Show quoted text

> Andreas Koenig via RT wrote:

>> Whazzat? Is this a known bug? That's an unhealthy tendency that people >> always believe that this perl is in the PATH. >> >> cpan[28]> install Carp::Assert >> Running install for module 'Carp::Assert' >> Running make for M/MS/MSCHWERN/Carp-Assert-0.18.tar.gz >> Is already unwrapped into directory >> /home/k/.cpan/build/Carp-Assert-0.18-JRZ16H >> >> CPAN.pm: Going to build M/MS/MSCHWERN/Carp-Assert-0.18.tar.gz >> >> Checking if your kit is complete... >> Looks good >> Writing Makefile for Carp::Assert >> make[1]: Entering directory `/home/k/.cpan/build/Carp-Assert-0.18-JRZ16H' >> cp lib/Carp/Assert.pm blib/lib/Carp/Assert.pm >> make[1]: pod2test: Command not found

Show quoted text

> The assumption here is that because Test::Inline is installed you > have pod2test in your PATH (look at MY::top_targets in the > Makefile.PL). That assumption appears to be broken in your case.

That's correct. If current perl is not in your path, then all programs that perl installs aren't either. Show quoted text

> So it can either A) use Test::Inline directly rather than go > through an intermediate program or B) check if pod2test is in the > PATH.

Let me vote for (A) as the superior alternative:) -- andreas

Tue Jan 02 18:27:44 2007 mschwern [...] cpan.org - Correspondence added

0.19 should resolve this. It was too much work to move all of pod2test's functionality into Pod::Test and call it from a Makefile. Instead I changed Carp::Assert's Makefile so that it only tries to run pod2test if Pod::Test is installed AND the pod file from which the test is generated has changed. This should result in pod2test never being run during normal installation and its more like how a Makefile should work.

Tue Jan 02 18:27:47 2007 mschwern [...] cpan.org - Status changed from 'open' to 'resolved'