httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Schaefer <joe+apa...@sunstarsys.com>
Subject Re: pass_through options
Date Fri, 14 Jan 2005 21:45:23 GMT
Randy Kobes <randy@theoryx5.uwinnipeg.ca> writes:

[...]

> I'm not sure about how PAUSE will see the provided modules;
> a guess is that it will look for .pm files, which if they're
> autogenerated, would be a problem, but this could be handled
> by providing a dummy .pm file just listing the provided
> modules and versions, like mp2 does now.
>
> For the prerequisites (and I assume we're talking about
> the CPAN/CPANPLUS shell being able to follow them), if
> I understand CPAN.pm correctly, I think what's expected
> is that the top-level Makefile has the following structure,
> at the top:
>
> # blah
> # blah
> #    PREREQ_PM => {A::B=>q[1.2], C::D=>[3.4] }
> # blah
> # blah
> # --- MakeMaker post_initialize section:
>
> This comes from CPAN.pm's prereq_pm sub, where it opens
> up the generated Makefile and looks for PREREQ_PM (until
> /MakeMake post_initialize section/ is encountered). What
> might then work is that, in the generated top-level
> Makefile, include this preamble with the desired PREREQ_PM.

Looks ok to me.  Once we've finalized our APIs (and mp2.0 
gets released), I think we should try to get the indexing
sorted out by putting a few release candidates on CPAN.

-- 
Joe Schaefer

Mime
View raw message