At 7:57 AM +0000 3/25/04, Barbie wrote:
There seems to be a problem with CPANPLUS (or an associated module) that
occasionally doesn't acknowledge the prerequisite lists. I've noticed this
happening with my testing in recent weeks, at which point I try manually
testing to see if the module installs, which it generally does. On occasion
I've also tried the 'test' command from the cpanp shell and that works too.
It appears to be something specific to the way cpansmoke hooks into
CPANPLUS.

On windows this is fraught with problems anyway, as the return string from
IPC::Run, gets dropped 99% of the time in a FAIL or UNKNOWN report, which is
why my reports are largely cut'n'pasted by hand.

I have tried to look into this myself, but have not come close to figuring
out why. Unfortunately upgrading to CPANPLUS-0.49 for me at least has broken
the ability for cpansmoke to use CPANPLUS, so I can't test it any further at
the moment.

Hello Barbie, thanks for your reply to my message (the first one). Your assessment of the problem makes sense to me. I suspected something similar.


You might want to check whether that's because the module requires 5.8.x, as
several of the testers are still at 5.6.1. Personally I do try and test
everything I possibly can.

Sorry can't be of more help at the moment, but hopefully someone will have
more understanding of the problem than I and be able to fix it.

Barbie.

Well, my current batch of modules, those that I updated after late 2003, simply "use 5.006", so they should work with anything 5.6.0 and later. So only testers running 5.005 or earlier couldn't do anything with them.


(My older modules only require 5.004, since at the time of their development that was the newest available on Mac OS 9. The newer ones throw/use exceptions that are objects, which is why they require 5.006.)

-- Darren Duncan

Reply via email to