>>>>> On Tue, 3 Oct 2006 16:56:08 -0500, Ken Williams <[EMAIL PROTECTED]> said:
> On Oct 2, 2006, at 2:50 PM, Andreas J. Koenig wrote: >> You're right, that was a surprisingly well working hack. Makefile.PL >> wrote a *comment* into the Makefile that could be parsed out again. > M::B does something similar, it writes a file called _build/prereqs > that lists all the prereqs computed at runtime by the Build.PL script. AHHHH, I didn't see the importance of this sentence when I first read it. Now I was going through this thread again and it stands out so nicely. Is this part of the API? I do not find it in Module::Build::API. Can I take it for granted that _build/prereqs is available after Build.PL has run and can I just eval its contents and get a hashref of the prerequisites? Are subclassing developers instructed to not write anything else into this file? It seems to me this would solve my current problems wrt prereqs. For the record, the problem I currently have is that the original suggestion to use $req = Module::Build->current->requires(); $breq = Module::Build->current->build_requires(); can fail when the author has written a subclass of Module::Build. This happened with Error.pm and HTML::Mason. CPAN 1.88_56 works around the problem by falling back to the contents of META.yml. If I get _build/prereqs for granted, we can doubtlessly do better. Thanks, -- andreas