On Dec 11, 2007 11:41 AM, Thomas Wittek <[EMAIL PROTECTED]> wrote: > Hi! > > Recently I uploaded a Module [1] to CPAN that uses M::B for the build > process. > Now, when you try to install it CPAN fails at the test cases as some > dependencies are missing. > > Do I have to put all dependencies that are needed for "./Build test" > into 'build_requires'? > If yes, then 'requires' would be completely empty, as I have at least > one test for each module. > > Or do I have to do anything else to get CPAN to recognize my > dependencies correctly?
By a quick inspection, I think your sin was to release a distribution with only Build.PL and no passthru Makefile.PL. Some CPAN testers (among them, chris) do not install in their smoke servers the part of CPANPLUS necessary for running Build.PL alone and that leads to ugly failures. The default behavior (nonsense to me) is to try to generate automatically a Makefile.PL which misses all dependencies and have all but an inferred dist name and a version. That is a safe road to FAIL in most of the cases. I was plagued by that too, but only with an Acme module which I insist to leave that way. If the testers are using the CPAN shell, test proceeds smoothly for these distributions. So what you need is just use the M::B option "create_makefile_pl" as taught by the document in http://search.cpan.org/perldoc?Module::Build::Compat if you want to get past these failures by now. PS. You may want to add "configure_requires => 'Module::Build' " as well. But most CPANPLUS-based toolchain does not honor yet (or so I think). Regards, Adriano Ferreira > Thank you! > > [1] http://search.cpan.org/~twittek/Konstrukt-0.5-beta8/ >
