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

[Russ Allbery]

Dmitry Smirnov <onlyjob at member.fsf.org> writes:

> 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)

This change looks reasonable.  I'll try to get this into the next release.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>