Bug#659939: pod2man: no exit code & empty files left behind

[Dmitry Smirnov]

Package: perl
Version: 5.14.2-6
Severity: normal
Tags: patch

pod2man always exit with status 0 even if conversion failed.

Worse, empty files left behind, for example if invoked like

    pod2man /dev/null null.1 && echo OK

"OK" will be printed and empty file "null.1" will be created.

Empty file left by Pod::Simple because it create output file before content 
generation. If no content produced, empty file left behind.

On top of this pod2man always exit with status code 0 disregarding
conversion result.

The attached patch addresses both problems. (Sorry for not making test case 
for this)

Regards,
Dmitry.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pod2man_exit-status.patch
Type: text/x-patch
Size: 1217 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/perl-maintainers/attachments/20120215/bb27c6db/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/perl-maintainers/attachments/20120215/bb27c6db/attachment-0001.pgp>