Bug 2815 - Improve fax2tiff scriptability
: Improve fax2tiff scriptability
Status: RESOLVED LATER
: libtiff
default
: unspecified
: PC Linux
: P2 enhancement
: ---
Assigned To:
:
:
: migrated_to_gitlab
:
:
  Show dependency treegraph
 
Reported: 2018-09-16 11:39 by
Modified: 2019-10-01 14:21 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2018-09-16 11:39:14
While investigating Bug 2814 I found it very difficult to script fax2tiff since
it exits with code 0 and produces a partial TIFF file on failures in the
copyFaxFile function.  It would be nice if fax2tiff could exit with a a
non-zero code to make failure easier to detect by calling programs.

I'd also suggest removing the partial output file, but I'm not sure if it might
have use in some error conditions.  Take that for what it's worth.

Thanks for considering,
Kevin
------- Comment #1 From 2019-02-13 05:15:10 -------
there could be a special error code for partial failures
------- Comment #2 From 2019-10-01 14:21:24 -------
Bugzilla is no longer used for tracking libtiff issues. Remaining open tickets,
such as this one, have been migrated to the libtiff GitLab instance at
https://gitlab.com/libtiff/libtiff/issues .

The migrated tickets have their summary prefixed with [BZ#XXXX] where XXXX is
the initial Bugzilla issue number.