Andy Lester wrote:
On Sep 11, 2005, at 7:25 PM, chromatic wrote:
I don't feel as confident as you do that if the tests all passed on your
machine that they'll automatically pass everywhere.
THIS is my biggest point. It's not about the quality of the code so
much as making sure the code fits with the target machine.
Well, it's not like I routinely bundle every single build-time
dependency just because I can. I do have some idea what I'm doing.
For the most part the bundled modules are
a) Mine, but one of the less common/popular ones
b) Have 100% PASS ratings on cpan testers
c) Are 1.00, which in my book at least means "complete, and/or bug free
for a year"
Test::ClassAPI (76 PASSes)
Class::Inspector (9 PASSes, but I only released last week)
Config::Tiny (50-odd PASSes)
etc
etc
If the modules I'm bundling are mature and well tested, and it means the
"convenience" or 2 or 3 less modules to install, because they are only
needed for a tenth of a second during testing, and thus not at all in
it's debian deb deps, then yes, I'm going to bundle them.
I know the risks, and I accept them on behalf of my users.
Adam K
