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

[Ken W. <ke...@ma...>]

On Tuesday, October 14, 2003, at 11:18  AM, <kev...@ub...> 
wrote:

> Hi
>
> Toolchain:
> Module::Build v0.20
> Perl v5.8.0
>
> If my package contains a MANIFEST.SKIP file, then the build action
> (which has to be run before the manifest action)

The 'build' action doesn't need to be run before the 'manifest' action 
- I guess you mean the "perl Build.PL" step.


>  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.

They're both aware of MANIFEST.SKIP files, but the only purpose of a 
MANIFEST.SKIP file is to help auto-generate a MANIFEST file.  If you 
don't have a MANIFEST file, then that warning (or maybe something a 
little more friendly) should indeed be emitted.

However, I just noticed that projects that use MakeMaker *don't* emit 
any warnings in this situation.  I'm not sure what to make of that.  I 
sort of think they should, but maybe not.  Schwern?

  -Ken