Re: [Module::Build] Use of manifest action produces ExtUtils::Manifest warnings

[Michael G S. <sc...@po...>]

On Tue, Oct 14, 2003 at 05:18:06PM +0100, kev...@ub... wrote:
> If my package contains a MANIFEST.SKIP file, then the build action
> (which has to be run before the manifest action) results in a
> warning of the following form:
> 
> Checking whether your kit is complete...
> MANIFEST: No such file or directory at
> .../perl/5.8.0/lib/ExtUtils/Manifest.pm line 182
> 
> Currently, I work around this by touching the MANIFEST file in
> a wrapper makefile.  However, I would think that either M::B or
> ExtUtils::Manifest (not sure which) needs to be updated to be
> aware of MANIFEST.SKIP files.

It looks like Module::Build::base::new() is calling check_manifest()
and then whinging because it doesn't exist.

Module::Build should check for the existence of a MANIFEST before
calling check_manifest() in that instance.

    $self->check_manifest if -r 'MANIFEST';

PS I'm not sure why MakeMaker makes calling check_manifest() conditional
on the Makefile not having been written.


-- 
Michael G Schwern        sc...@po...  http://www.pobox.com/~schwern/
Playstation?  Of course Perl runs on Playstation.
    -- Jarkko Hietaniemi