Well, I have two sets in my smoke directory, one for "maint" (Aka Perl 5.8.x) and one for "current" (Aka Perl 5.9.x). You didnt run perldoc yet did you? :-)

Seems to me that if Test::Smoke were included in the distribution, a) it would save another install step; b) it could be set up to test the distribution is was a part of and each distribution would be 'self-contained'.

Alternatively, a command line parameter to the batchfile could identify the relative path of the distribution to be tested.

And no, I didn't run perldoc yet. I thought I'd get through the first run with the default settings before getting sidetracked in to looking at what options were available and being tempted to try them out. Just trying to get a consistant set of notes written down vefore thinking about variations :)

Personally I'd just tell your firewall to ignore anything in the smoke tree.

I don't think my firewall has that option, (and I'm not sure I like the implications of it if it has), but I'll look into it.

BTW. The smoketest just finished. It ended with:

c:\Perl\src\run>smokecurrent.cmd
mkdir : No such file or directory at lib\archiverpt.pl line 115
[download]

I saw an option during configuration asking about archiving, I selected the default which I think was 'Don't keep an archive'. Does that explain the above message? Or has something failed that invalidates the test?

I was antisipating seeing some message telling me what to send where to complete the process, but I haven't. So, what should I be sending and where?

Note: I chose not to configure an email address during the setup. I don;t like automated transmissions--I like to know what is being sent--does that screw things up?

Phew! 9 hours and about 200 manual interventions. And I'm meant to do this daily?