Re: Module::Build+Apache::Test config looping issues redux

[Christopher H. Laco]

Stas Bekman wrote:

I meant, that I don't understand why do you get stuck at t/SMOKE? Are you trying to use it and it's not working? Or is it the TestMB that tries to create it and fails the whole thing, when you don't even want t/SMOKE? You really need t/TEST for the test suite. t/SMOKE is for advanced testing/debugging.

Oh, I see. Let's forget that I ever mentioned Module::Build and TestMB for a moment and stay in the realm of ExtUtils::MakeMaker.

Let's assume I've created a TEST.PL, SMOKE.PL and a Makefile.PL that calls generate_script("t/TEST") and generate_script("t/SMOKE").

If I run:

        perl Makefile.PL
        make
        perl t/TEST t/sometest

everything works fine. t/conf/apache_test_config.pm is auto-generated with the expected data from TestConfigData.pm.

Now, do a make distclean to start from scratch.

Now I run:

        perl Makefile.PL
        make
        perl t/SMOKE

t/conf/apache_test_config.pm is NOT generated, nor is any other file in t/conf. This is what starts the endless "where's apache.exe" loop for me under win32.

The lack of autogenerated A-T config files leads to the assumption that using t/SMOKE REQUIRES that you first run t/TEST to autogenerate the configs.

I don't remeber reading that requirement anywhere and was curious if perl t/SMOKE show act exactly like t/TEST and qutogenerate the needed t/conf files.

-=Chris
        

smime.p7s
Description: S/MIME Cryptographic Signature