[Bioperl-l] Re: undef

[Aaron J Mackey]

Right; the PL_FILES functionality is to allow makefile "targets" that are
produced/updated by a .PL script.

Since we now have Bio::Root::Version taking care of *.pm files, I think
the only reason we need makedoc.PL is for text-only documentation files
(i.e. pod's), and it makes sense to me that we list them explictly here,
and use makedoc.PL's @ARGV to find out what files to run on.  It all seems
so explicit.

-Aaron

On Wed, 12 Mar 2003, Brian Osborne wrote:

> Aaron,
>
> No, I don't think my idea of using 'undef' is a good one, I see what
> MakeMaker is doing now. Currently the Makefile has:
>
> makedoc :: doc/makedoc.PL
> <some stuff>
>         $(PERLRUNINST) doc/makedoc.PL makedoc
>
>
> But with 'undef' it is:
>
>               :: doc/makedoc.PL
> <some stuff>
>         $(PERLRUNINST) doc/makedoc.PL makedoc
>
> And this didn't execute makedoc.PL when I ran 'make'.
>
> Your idea makes most sense if makedoc.PL actually does something with its
> arguments. Your proposal would create something like:
>
> makedoc :: doc/makedoc.PL
> <some stuff>
>         $(PERLRUNINST) doc/makedoc.PL biodatabases.pod bioperl.pod
> biodesign.pod
>
> I know you know that, I'm being explicit here. So instead of makedoc.PL
> using File::Find we could ask it to use @ARGV, etc. Presumably there will
> never be many *pod documents. The beauty of File::Find, as you suggested,
> was that it could be used on all *pm files, that would be lost.
>
>
> Brian O.
>
>

-- 
 Aaron J Mackey
 Pearson Laboratory
 University of Virginia
 (434) 924-2821
 amackey at virginia.edu