Update of bug #67612 (group groff):
Summary: gropdf has nonzero exit on warning => [gropdf] exits
with nonzero status on warning
_______________________________________________________
Follow-up Comment #2:
[comment #1 comment #1:]
> Ah, the problem isn't tied to this warning in particular. The
> [http://git.savannah.gnu.org/cgit/groff.git/commit/?id=6198245ea commit
> 6198245ea] log says, "src/devices/gropdf/gropdf.pl: Exit with code 2 if any
> warnings issued during run (this will stop a 'make')."
>
> But it seems to go against the very concept of a warning to stop a build
> because of one. "make" builds plenty of code that spits out compiler
> warnings, and developers would be very cross were that to change: the whole
> reason something is a warning is so a human can evaluate whether it's an
> actual problem. If something rises to the level of "stop 'make'," it should
> be an error, not a warning.
I concur. I think a better solution would be for _gropdf_ to support a
command-line option or environment variable that caused it to treat warnings
as fatal problems.
> This warning in particular doesn't even fit the definition of "warning" that
> that commit added to the man page: "PDF produced may be usable, but it will
> have issues." There seems no way a warning about a slow run time can result
> in issues in the produced PDF; it just means you wait longer for it.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67612>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
