Hi Aristotle, (in portuguese your name is written "AristÃteles":)
I can't believe noone understood what you were talking about and went off to lala-land. :-/
:-) hehehehe "lala-land", that was fun! Yes, they simply ignored what I asked them.
Even if I use the technique you suggested, when an automated cpan-tester went to install my module, it will fail if it didnÂt have daemontools installed, right?
I updated my test script avoiding it to fail if it canÂt find the daemontools package installed. I would like to print a warning message to the STDERR in order to advise about it, but I donÂt know how a cpan-tester would react if it find some output to STDERR...
What do you know about it?
Thanks, bnegrao
I was not ignoring your problem. Other than what had already been sugested there is currently no way to elegantly solve your problem which is why I wanted to discuss alternative mechanisms to solve this problem in the future. Hopefully you will soon be able to solve your problem by editing the META.yml file in your distribution. For now your only options are to skip or fail during 'make test' or to abort during 'perl Makefile.PL'. Most module authors choose the later.
Regards, Randy.
