Re: [hylafax-users] Hylafaxplus is not compatible with libtiff 4.6.

[Lee H. <fa...@ho...>]

On 9/29/23 10:33 PM, Max Mothwurf wrote:
> Hello Lee,
>
>>> what is your recommendation for the moment?
>>> (I just hit the same trap in openSUSE Tumbleweed)
>> For the moment people using HylaFAX+ servers should not use libtiff v4.6.0 and should consider v4.6.0 to be broken.  So, use v4.5.1 instead.
> That is difficult in a rolling release.
> (Although I would not recommend to use hylafax on Tumbleweed (TW), as all packages have to go through Factory/TW first, it will be removed soon if it fails to compile)
> Any other workaround?

It's going to take some time (months, probably) before enough libtiff 
users who rely on the tools and features that were removed in libtiff 
v4.6.0 to notice what has happened and to either pressure libtiff 
developers to backtrack or to produce a "tiff-tools" package or something.

Although I am willing to do it eventually, I am not anxious to do the 
considerable work that will be required to change how HylaFAX does 
things to avoid using the tools and features or to fork the tools code 
into HylaFAX - only to see a while later that libtiff developers 
backtrack and restore the tools and features in a later release or the 
community produces a "tiff-tools" package.

I have been in communication with libtiff users who are mostly 
interested in doing the necessary code work to encourage libtiff 
developers to backtrack.  That would be my preferred option, too, but as 
of yet I do not see any traction with libtiff developers. So, I am 
wishful about it, but not hopeful.  It's going to take some time for 
them to try that before they turn to a "tiff-tools" package.

For distributions with rolling releases, they undoubtedly encounter this 
kind of problem regularly and surely must have a typical strategy on how 
to deal with this situation.  So, they should do that - whatever it is.

Thanks,

Lee.