Re: [Module::Build] .PL files && Module::Build

[Randy W. S. <Ra...@Th...>]

On 1/15/2004 10:01 AM, Jaap Karssenberg wrote:
> Greetings,
> 
> I'm trying to move a rather large package to Module::Build. It has lot's
> of custom built-time config so I moved away from MM a while ago and have
> used a hack for a while.
> 
> I have to rely on .PL files a lot now to do config stuff and I was
> wondering whether there is an interface in Module::Build to get build
> variables. Basicly I want to know the run-time equivalent of the
> contents of _build/build_params. The hack would be to read build_params
> myself, but this won't be portable I guess; also if the user supplies
> commandline arguments to ./Build they get ignored. 
> If Module::Build does not provide this (yet) I will write a patch that
> ads an option to dumps the run-time variables to a tmp file.

What config information do you need? Why? There needs to be a good 
reason for a module to expose any of its private data.

Commandline arguments are not ignored; can you elaborate? What did you 
try? What did you expect?

> Do you plan to have the 'checkdeps' (check dependenies) and
> 'installdeps' (install dependencies from CPAN) actions ?
> Would you include these if I send you a patch ?

One of the first things Module::Build does when it's run is check 
dependencies and then display any that are missing. For automatically 
installing dependencies, see CPAN.pm, CPANPLUS, & Module::Install.

> Nice work so far, like it better then MM allready :)
> 
> 	Jaap Karssenberg <pa...@cp...>
> 
> PS. sorry for not directly using the list - didn't see it at first
> 
> P.P.S. And another question, where do I leave extra manpages for section
> 1, could there be a equivalent for 'pod_files', 'pod1_files' or
> something similar ?

I'm not sure how to answer this one. Why would you have POD that belongs 
in section 1 that does not belong to a script?

Regards,
Randy.