Return-Path: <SRS0=I4kx=JT=lists.osgeo.org=tiff-bounces@osgeo.org>
Delivered-To: filtered@awaresystems.be
Received: from mx2.pub.mailpod8-cph3.one.com ([10.27.38.12])
	by mailstorage22.cst.mailpod8-cph3.one.com with LMTP
	id cDBABmXKx2ULOgAAwT5NuQ
	(envelope-from <SRS0=I4kx=JT=lists.osgeo.org=tiff-bounces@osgeo.org>)
	for <filtered@awaresystems.be>; Sat, 10 Feb 2024 19:11:33 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=custmx.one.com; s=20201015;
	h=sender:content-transfer-encoding:content-type:reply-to:from:list-subscribe:
	 list-help:list-post:list-unsubscribe:list-id:subject:mime-version:message-id:
	 in-reply-to:date:references:to:x-halone-refid:x-halone-sa:from:x-halone-sa:
	 x-halone-refid;
	bh=mnUr6vPo2zyTSUNRVna/WOGxForTs2HEMzxsiyjDFP0=;
	b=rM8la+Zmzc0gT8l+d8KQLh2VyqH+1akB4UUlgIfNHVwUKSyZyeQaNpsNBX3Kis3tG5gLXy4xP6jmd
	 +G0mlTMlr4CDRRDauZwLIR3GCwcP5ahCZkoWz9M99T2Tnki2nERYkhOccFTyfKnnNJYta2QxRcZqNn
	 jD9Hb0AKfR0Y8YP5CzE1PUu0z1sr20qhlol5ozuORtY8Ffxk9eLHylIbBGjdVfooQdsCiJEqbCglvy
	 LsHYL1PuEhpg141JKqswajcV+O4FZXdpXQ7xrQTuz/9Get84DNzQXtGqJOR+wNZ8jI/ySoXPRU3X9r
	 gYnjL6ZAmZA6Z0VCGu6UP0xkGKFLscA==
X-HalOne-SA: -1
X-HalOne-RefID: 155866::1707592292-7C3D3217-A463E7BC/0/0
Authentication-Results: mx2.pub.mailpod8-cph3.one.com;
	spf=pass smtp.mailfrom=osgeo.org smtp.remote-ip=140.211.15.3;
	dmarc=pass header.from=lists.osgeo.org;
X-HalOne-ID: 3359f333-c848-11ee-8619-98039b05783e
Received: from lists.osgeo.org (osgeo6.osgeo.osuosl.org [140.211.15.3])
	by mx2.pub.mailpod8-cph3.one.com (Halon) with ESMTP
	id 3359f333-c848-11ee-8619-98039b05783e;
	Sat, 10 Feb 2024 19:11:32 +0000 (UTC)
Received: from osgeo6.osgeo.osuosl.org (localhost [127.0.0.1])
	by lists.osgeo.org (Postfix) with ESMTP id 592DC6144EA9;
	Sat, 10 Feb 2024 11:11:30 -0800 (PST)
Received: from s1.lexort.com (s1.lexort.com [71.19.148.97])
 by lists.osgeo.org (Postfix) with ESMTPS id DD3356146801
 for <tiff@lists.osgeo.org>; Sat, 10 Feb 2024 11:11:28 -0800 (PST)
Received: by s1.lexort.com (Postfix, from userid 10853)
 id 65BFD41070F; Sat, 10 Feb 2024 14:11:28 -0500 (EST)
To: Holger Bruenjes via Tiff <tiff@lists.osgeo.org>
References: <a7345b73-3cfa-965c-0e8e-0d313d2b0b69@spatialys.com>
 <rmijzstan86.fsf@s1.lexort.com> <rmir0hk76m5.fsf@s1.lexort.com>
 <28b88672-6cb9-460c-8adc-00c6869a4908@bru.lan>
OpenPGP: id=098ED60E
Date: Sat, 10 Feb 2024 14:11:28 -0500
In-Reply-To: <28b88672-6cb9-460c-8adc-00c6869a4908@bru.lan> (Holger Bruenjes
 via Tiff's message of "Sat, 10 Feb 2024 15:25:32 +0100")
Message-ID: <rmiy1bs5e3j.fsf@s1.lexort.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (berkeley-unix)
MIME-Version: 1.0
Subject: Re: [Tiff] libtiff 4.6.0 is released
X-BeenThere: tiff@lists.osgeo.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.osgeo.org>
List-Unsubscribe: <https://lists.osgeo.org/mailman/options/tiff>,
 <mailto:tiff-request@lists.osgeo.org?subject=unsubscribe>
List-Post: <mailto:tiff@lists.osgeo.org>
List-Help: <mailto:tiff-request@lists.osgeo.org?subject=help>
List-Subscribe: <https://lists.osgeo.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.osgeo.org?subject=subscribe>
From: Greg Troxel via Tiff <tiff@lists.osgeo.org>
Reply-To: Greg Troxel <gdt@lexort.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tiff-bounces@lists.osgeo.org
Sender: "Tiff" <tiff-bounces@lists.osgeo.org>

Holger Bruenjes via Tiff <tiff@lists.osgeo.org> writes:

> Hello
>
> Am 10/02/2024 um 15.10 schrieb Greg Troxel via Tiff:
>> Greg Troxel <gdt@lexort.com> writes (in *September 2023*):
>>
>>> I am really unclear on whether there will be fallout from tools removal.
>>> Again not a complaint; I just don't like surprises.  My expectation is
>>> very little to maybe none, and that if so it will be run time not
>>> build/install/package time.  So if anyone updates tiff in a packaging
>>> system, and does or doesn't find issues, I would appreciate a note here
>>> from fellow packagers.  I'll post myself after updating.
>>
>> I updated tiff in pkgsrc on October 16.
>>
>> So far, the only thing broken is hylafax, which errors out at configure
>> time not finding tiff2ps.  I realize this is very well known, but I'm
>> not clear on packager consensus about how to deal with current situation.
>>
>> Hylafax's last change was in 2018:
>
> HylaFAX+ is actively under development by Lee Howard many years ago
>
> see -> https://hylafax.sourceforge.io
>
> and the change in project libtiff-> 4.6.0 is fatal for the tiff
> tools used in HylaFAX+.

OK, but it seems that "hylafax.org" is not maintained.   Does ~everybody
think that hylafax.org is no longer relevant to anything?

Is "HylaFAX+" a continuation fork viewed by the community as
established, and therefore this sourceforge repo is the proper upstream
for the package known as hylafax?  Or is that hylafax the package is not
maintained and packagers should add a hylafax+ package instead?

I see that HylaFAX+ had a release in January 2023 -- but apparently not
one that works with libtiff 4.6.0.
_______________________________________________
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff
