Re: [Module-build-general] Hello and manifypods
Status: Beta
Brought to you by:
kwilliams
|
From: Steve P. <sp...@ep...> - 2003-07-16 08:13:58
|
On Wednesday, July 16, 2003, at 12:26 am, Ken Williams wrote:
> On Monday, July 14, 2003, at 04:15 PM, Dave Rolsky wrote:
>
>> On Mon, 14 Jul 2003, Steve Purkis wrote:
>> - Section 1 pods should be generated based on the files found by
>> $self->find_script_files, I think.
>>
>> - Section 3 pods should be generated based on $self->find_pod_files,
>> and
>> $self->find_pm_files. These are higher level than running
>> ->rscan_dir and
>> allow the module maintainer to specify which files to process. If you
>> just run rscan_dir yourself you'd be ignoring that.
>
>
> 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.
Should we also look in blib/bin for section 1 pods, or does that only
ever contain binaries (ie: no shell scripts)?
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.
PS: patch half-written, but won't likely have time to finish 'till
Friday.
-Steve
|