Date: Wed, 16 Feb 2000 23:24:57 +0100 (CET) From: hmo@sep.hamburg.com (Helge Oldach) To: billf@chc-chimes.com (Bill Fumerola) Cc: matthias@mscu.snafu.de, faq@hylafax.org, ports@freebsd.org Subject: Re: FAQ suggestion for HylaFAX Message-ID: <200002162224.XAA28799@sep.hamburg.com> In-Reply-To: <20000216164831.R92177@jade.chc-chimes.com> from Bill Fumerola at "Feb 16, 2000 4:48:31 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Bill, | (2) This patch depends on the work directories of those ports to exist. | The dependencies don't reflect this. This was meant as a quick workaround. The current hylafax port is not only BROKEN because of security issues (which were fixed as of 4.1beta2), but also because 4.0pl2 really depends on the tiff-3.4 libraries that went out of the port collection some time ago. Hylafax 4.0pl2 does strange things if linked against tiff-3.5.3 from ports-cur. Again, this is a workaround for current FreeBSD hylafax users who decided to live with the security issue. The correct way to deal with this issue of course is to upgrade the port to hylafax 4.1beta2 (which not only appears to be quite stable in non-FreeBSD environments but also fixes the BROKEN issue) and crosscheck that against current libtiff. Take Matthias' mail as an informational message, please. Regards, Helge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002162224.XAA28799>