[hylafax-devel] Outstanding work for 4.1beta3

[Phil Watkinson <Pkwatkinson@tesco.net>]

Robert <rjc@trump.net.au> wrote to Darren <darren@dazza.org>
> There  are a few of options i can think of:
>
> 1) Leave patch as is, will require people to upgrade to 3.5.X, this will
> require the least amount of work.
>
> 2) Wrapper run length quantities and add some logic to configure to detect
> different versions of the tiff library.
>
> 3) Try and separate hylafax and libtiff a little better so that hylafax is
> not dependent on internal libtiff routines, by far most work but probably
> best result.
>

I vote for (1) - are we voting? - libtiff 3.5.x is not going to go away
and there could be a patch to 'downgrade' HylaFAX back to libtiff 3.4
for those platforms where libtiff 3.5 is not available.

If I have been paying attention, list of outstanding matters for the
release of v4.1beta3 is as follows :

1. Decision on libtiff fix
2. Change to configure to check for correct libtiff library
3. Sun OS patches - munmap.patch, RAND_MAX.patch and mkdepend.patch
      by Nico Kadel-Garcia and James Lee
4. Decision on removing '/bin/stty' warning messages on Linux boxes
5. seqf file fix to hfaxd/HylaFAXServer.c++
6. Tim said don't forget to update functions ModemServer:beginSession
   (in faxd/ModemServer.c++) and FaxServer:getRecvFile (in faxd/
   FaxRecv.c++)
7. Dmitry's RTN (and other) fixes we heard about tonight.
8. The SuSE patch to discard ip-sourced packets
9. A fix to the manpage script to prevent a gaping security hole.

Any others (AIX patches from Steve Wiliams??)

Getting there!
Regards,
Phil.






____________________ HylaFAX(tm) Developers Mailing List ____________________
 To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < /dev/null