On Dec 28, 2004, at 1:53 PM, Stas Bekman wrote:
'perl' => 6.006,
perl 6? :)
Oops. :-)
why Apache::TestMB? It should be ModPerl::MB when it'll appear, right?
Up to you. I used it as an example because I don't really understand how Apache::TestMM and ModPerl::MM interact.
why the fallback for Module::Build? Shouldn't it just die then?
No, because if you're installing from CPAN.pm, it should install Apache::Test. I think. The build_class parameter is actually a much better choice, since you won't have to worry about that at all. Again, that should be in 0.27 of M::B (not sure of a due date).
what if none exists, should Module::Install be used to require Module::Build?
No idea. I've never used Module::Install. You'll have to ask autrijus.
when will that be released? I guess I need to require that version then.
Ask Ken.
So the only remaining part is to override Module::Build to place modules under Apache2/ if mp2 was built this way. Could you post an override that unconditionally overrides that and I'll adjust it to figure it out dynamically?
Uh....might be tricky. There's been a lot of debate about install paths on the Module-Build list lately. I'd ask there. The install paths are set up by the _set_install_paths() method in Module::Build::Base.
http://search.cpan.org/src/KWILLIAMS/Module-Build-0.2607/lib/Module/ Build/Base.pm
On Dec 28, 2004, at 1:56 PM, Stas Bekman wrote:
what if none exists, should Module::Install be used to require Module::Build?
that's a tricky one. If ModPerl::MB is added, I suppose a Build.PL writer should still manually require Module::Build (version) and probably ensure that it's installed via Module::Install, correct? Then ModPerl::MB could check for a specific version of it.
Again, I know nothing about Module::Install.
Regards,
David
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
