# from Christopher H. Laco
# on Monday 30 July 2007 01:35 pm:
>If it fails and you can't install it, then don't.
>Arguments about whether the tests should or shouldn't be run [or
>included at all] is irrelevant. Tests failed. Don't install.
I think you're looking at this as "oh, I'll try whiz-bang module foo."
Sure, you can just dismiss it, but that's really not the concern. It
is quite relevant when we get 2-3 levels deep in dependencies and
somebody made a slight slip or added a new dependency which fails for
this reason.
Then we end up digging through a customer e-mail trying to sort through
what went wrong and finding that a lot of time has been lost on
something very simple and "dismissable".
And then, it turns out that this is a situation which the "perl qa
community" has encouraged, condoned, and rewarded even. Gah! Where
was I during that vote?
>File RT.
Won't happen. Not ~95% of the time anyway.
>If
>the author made a choice to have them run always and piss people off,
> or restrict the user base, then that's the authors prerogative.
In most cases, it is not the author's deliberate choice that these
things happen, instead, it is believed to be some sort of mandate that
they be in the distro "because Module::Starter put them there" or
"CPANTS says I should have them."
That is, the vast majority of authors who have them have not worked
through the logic of what damage these tests do on the install side.
--Eric
--
Any sufficiently advanced incompetence is indistinguishable from malice.
--The Napoleon-Clarke Law
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
