Re: [Module-build-general] Hello and manifypods
Status: Beta
Brought to you by:
kwilliams
|
From: Ken W. <ke...@ma...> - 2003-07-16 14:48:36
|
On Wednesday, July 16, 2003, at 03:13 AM, Steve Purkis wrote:
> On Wednesday, July 16, 2003, at 12:26 am, Ken Williams wrote:
>>
>> Section 3 pods should probably be generated from blib/lib and
>> blib/arch, and section 1 pods should be generated from blib/script.
>> This is because theoretically, the process of copying lib/* to
>> blib/lib/* and the like can do all kinds of transformations on the
>> POD. For instance, in Mason we can transform some special P<> tags
>> to normal POD.
>
> Easy enough - I can just do an rscan of those dirs then. That also
> answers my concerns about checking for pod in .c, .xs, and other > files.
Yup.
>
> Should we also look in blib/bin for section 1 pods, or does that only
> ever contain binaries (ie: no shell scripts)?
That's a good question - I don't *think* it ever contains shell
scripts, but in truth I actually have no idea. We might have to punt
on this until we hear what the right behavior should be.
>
> Also, would it be a good idea to have a customizable set of dirs in
> say $self->{properties}{manify} ala:
>
> section1 => [qw( blib/scripts )]
> section3 => [qw( blib/lib blib/arch )]
>
> That way, if something gets missed at least the user can override it.
Yeah, that's a good idea.
-Ken
|