Thread: [Module::Build] .PL files && Module::Build
Status: Beta
Brought to you by:
kwilliams
|
From: Jaap K. <j.g...@st...> - 2004-01-15 15:15:27
|
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. 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 ? 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 ? -- ) ( Jaap Karssenberg || Pardus [Larus] | |0| | : : http://pardus-larus.student.utwente.nl/~pardus | | |0| ) \ / ( |0|0|0| ",.*'*.," Proud owner of "Perl6 Essentials" 1st edition :) wannabe |
|
From: Randy W. S. <Ra...@Th...> - 2004-01-17 20:17:24
|
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. |
|
From: Jaap K. <j.g...@st...> - 2004-01-19 17:56:40
|
On Sat, 17 Jan 2004 15:17:52 -0500 Randy W. Sims wrote: : On 1/15/2004 10:01 AM, Jaap Karssenberg wrote: : > 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. For compatibility with the many other packaging modules it might be nice to have default support for the "checkdeps" and "installdeps" actions. Checkdeps would indeed not add any functionality but some users and frameworks expect it to be there. Installdeps would indeed use CPAN, CPANPLUS or Module::Install. : > 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? Perl has it :) Also I want to package a "devel" and a "faq" page with my program. I know some people argue this should be just one big page, but I like to keep it seperated, matter of taste I'm afraid. -- ) ( Jaap Karssenberg || Pardus [Larus] | |0| | : : http://pardus-larus.student.utwente.nl/~pardus | | |0| ) \ / ( |0|0|0| ",.*'*.," Proud owner of "Perl6 Essentials" 1st edition :) wannabe |
|
From: Ken W. <ke...@ma...> - 2004-01-18 15:20:20
|
On Thursday, January 15, 2004, at 09: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; By "run-time", do you mean during "Build test", or after the module is installed? If it's the former, you can use the Module::Build->current() method, then use the interface of the returned object. If it's the latter, M::B currently doesn't have much to help in this area. -Ken |
|
From: Jaap K. <j.g...@st...> - 2004-01-19 17:48:00
|
On Sun, 18 Jan 2004 09:20:19 -0600 Ken Williams wrote: : > 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; : : By "run-time", do you mean during "Build test", or after the module is : : installed? If it's the former, you can use the : Module::Build->current() method, then use the interface of the : returned object. If it's the latter, M::B currently doesn't have much : to help in this area. I need the former to "compile" values into my program so I can accomplish the later :) The Module::Build->current() method will do nicely, thanks. -- ) ( Jaap Karssenberg || Pardus [Larus] | |0| | : : http://pardus-larus.student.utwente.nl/~pardus | | |0| ) \ / ( |0|0|0| ",.*'*.," Proud owner of "Perl6 Essentials" 1st edition :) wannabe |