# from David Cantrell on Tuesday 06 November 2012:
>> So how would I fix the dependency problem if I don't even know about
>> it?
>
>By testing your code before releasing it? ... For the few of my dists
>that I care most about,I re-test them every so often to make sure that
>CPAN didn't break them.
The problem comes after you have released your code and its
installability gets broken by a dependency's new bug/failure.
In theory, you shouldn't have to retest your code to catch this (and I
agree that reporting as a failure against your code is also incorrect.)
That said, I would probably opt-in to some e-mail that tells me when a
dep revision introduced a failure such that one of my dists became
uninstallable, but I could also probably find a way to make that into a
cron job using currently available data/APIs.
--Eric
--
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
