On Sat, Nov 03, 2007 at 12:04:57PM -0500, Matthew Musgrove wrote: > >>'xapian-config' is not recognized as an internal or external command, > >>operable program or batch file. > >>xapian-config not found - if Xapian isn't installed on your PATH you can > >>run as: perl Makefile.PL XAPIAN_CONFIG=/path/to/xapian-config > >I think the error message makes it pretty clear why the build has failed > >- you don't have the Xapian library installed, or haven't installed it > >so that xapian-config is on your PATH. > > > >Please don't mail me about builds which fail like this - it's not a bug > >in Search::Xapian, so it's just junk mail. > You're frustration is understood but without a way for my automated > testing script to know what your module relies on I have no way of > telling it not to try and install it.
Until we've figured out a way of automating this (Devel::CheckLib goes a long way towards this but isn't finished yet, and I can see I'm going to have to also do Devel::CheckExecutable!) then I strongly recommend defaulting to *not* sending failure reports for the 'Makefile.PL' and 'make' stages. The appropriate lines from my .cpanreporter/config.ini are: send_PL_report=unknown:ask/no fail:ask/no pass:no na:no send_make_report=unknown:ask/no fail:ask/no pass:no na:no That way I won't accidentally send bogus reports like that one, but provided I'm paying attention I *can* send reports for errors such as the author requiring but forgetting to bundle Module::Install. Replies to cpan-testers-discuss please. -- David Cantrell | London Perl Mongers Deputy Chief Heretic What profiteth a man, if he win a flame war, yet lose his cool?
