Re: [Module::Build] codebase? paths in .tar.gz?

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

On Friday, December 19, 2003, at 04:05  AM, Randy W. Sims wrote:
>
> This is happening because M::B didn't find an abstract (this comes 
> from the pod, =head1 NAME section). I'm not sure, but in PPMMaker.pm 
> lines 22-25 I think all of these fields should be required (name, 
> author, abstract, version) and we should die with a usefull message if 
> not found. Ken?

Agreed.

> On 12/19/2003 4:30 AM, Glenn Linderman wrote:
>
>> This produces a pretty nice looking result, real corresponding to 
>> other .ppd files for other modules with similar requirements.  But 
>> apparently there are a couple bugs in the build ppd that produce the 
>> warnings above.
>> And so I'd like to see a "fix" to allow CODEBASE to default to the 
>> name of the .tar.gz file built by "build dist", and then people that 
>> want something more complex can still provide the command line 
>> override, or the build.pl file setting, or whatever.  But the above 
>> type of PPD can be copied from spot to spot, together with keeping 
>> the .tar.gz in the same directory, and works great.
>
> Ok, I agree with this, with the caveat that M::B should print out an 
> informational message saying what it is using a default.

Done.

>> Yeah, they went away like magic, once YAML was installed.  Just more 
>> dependency-itis to deal with.
>
> This still needs some kind of fix. If YAML is not available, M::B 
> should handle it more gracefully...
>

It's possible we could produce the META.yml without using YAML.pm, but 
the META.yml does need to be produced.  At this point it's a real error 
not to have YAML.pm installed.

  -Ken