I've just finished beating my head against the modperl tests. I
understand that I'm not alone in having been down this route.
I also understand from trawling through the mailing list archives - a
not entirely pain-free procedure itself - that the mod_perl 'grown-ups'
are "getting tired" of answering questions about failing tests,
particularly those about content_length_header.t and status.t.
Also, I note from my trips through the archives that I am not alone in
thinking that the tests should work 'out of the box'. Darryl Miles - I
too feel your pain (and frustration).
And all this pain would be prevented by the simple addition of a 'Known
issues with the tests' section on the web site. Heck, you even have a
section entitled "'make test' Failures" in the documents already. How
hard would it be to keep the current known issues up to date in this
document (or at least add a reference to a page on which they were
recorded)?
Don't get me wrong - I appreciate the work all the good boys and girls
of open source freeware land do for us all. But we have a communication
issue here, where both sides are getting frustrated and it seems that
the fix could be so trivially simple that it makes NO sense not to do
it?
And now I'm going back to my day job (which is actually *using*
mod_perl, not working out why tests are failing!)
Later,
Andy
-------------
Yada, yada, yada...
The information contained in this e-mail (including any attachments) is
confidential and is intended for the use of the addressee only. The
opinions expressed within this e-mail (including any attachments) are
the opinions of the sender and do not necessarily constitute those of
Roslin Institute (Edinburgh) ("the Institute") unless specifically
stated by a sender who is duly authorised to do so on behalf of the
Institute.
