2024.02.10 17:44 "Re: [Tiff] libtiff 4.6.0 is released", by Bob Friesenhahn

I am inclined to take the position:

hylafax is unmaintained and it's just aging out of working. While that's unfortunate, it needs to be fixed upstream and it's not reasonable to expect packaging systems to work around problems in software whose last release was over 5 years ago.

Another approach is to create a tiff2ps split package that builds tiff2ps anyway, and have hylafax also depend on that, if someone wants to make hylafax work. I don't think it is reasonable to enable tiffp2s in the main tiff package.

Hylafax is still maintained. Its maintainer (Lee Howard) was perhaps not aware at the time that removing the libtiff tools was being discussed (briefly) on the tiff mailing list. Others did express some concern at the time due to their own usage.

Unfortunately, the libtiff tools which were removed (and which Hylafax uses) also use libtiff internals since they were expected to be built along with libtiff.

I can't attest to what distribution mainainers may do, but Hylafax is clearly broken if only provided with the libtiff 4.6.0 update.

Bob

Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt