Return-Path: <awaresystems.be+caf_=filtered=awaresystems.be@gmail.com>
X-Original-To: filtered@awaresystems.be
Delivered-To: filtered@awaresystems.be
Received: from mx-r.one.com (mx-r.one.com [91.198.169.249])
	by mail9.b-one.net (Postfix) with ESMTP id A000A400913
	for <filtered@awaresystems.be>; Mon, 23 Jan 2012 16:12:37 +0100 (CET)
X-Virus-Scanned: by one.com
Received-SPF: pass (mx-r: domain of awaresystems.be+caf_=filtered=awaresystems.be@gmail.com designates 209.85.160.48 as permitted sender)
X-Greylist: whitelisted by SQLgrey-1.8.0-rc2
Received: from mail-pw0-f48.google.com (mail-pw0-f48.google.com [209.85.160.48])
	by mx-r.one.com (Postfix) with ESMTP id 17C32C4F11A
	for <filtered@awaresystems.be>; Mon, 23 Jan 2012 15:12:36 +0000 (UTC)
Received: by pbff6 with SMTP id f6so676987pbf.21
        for <filtered@awaresystems.be>; Mon, 23 Jan 2012 07:12:35 -0800 (PST)
Received: by 10.68.74.233 with SMTP id x9mr22622178pbv.74.1327331555729;
        Mon, 23 Jan 2012 07:12:35 -0800 (PST)
X-Forwarded-To: filtered@awaresystems.be
X-Forwarded-For: awaresystems.be@gmail.com filtered@awaresystems.be
Delivered-To: awaresystems.be@gmail.com
Received: by 10.143.13.20 with SMTP id q20cs40034wfi;
        Mon, 23 Jan 2012 07:12:32 -0800 (PST)
Received: by 10.68.74.164 with SMTP id u4mr22786137pbv.85.1327331550639;
        Mon, 23 Jan 2012 07:12:30 -0800 (PST)
Received-SPF: softfail (google.com: best guess record for domain of transitioning tiff-bounces@lists.maptools.org does not designate 91.198.169.58 as permitted sender) client-ip=91.198.169.58;
Received: by 10.68.3.162 with POP3 id d2mf2465699pbd.24;
        Mon, 23 Jan 2012 07:12:30 -0800 (PST)
X-Gmail-Fetch-Info: info@awaresystems.be 1 pop.awaresystems.be 110 info@awaresystems.be
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-k.one.com (mx-k.one.com [91.198.169.58])
	by mail9.b-one.net (Postfix) with ESMTP id B8CF5400913
	for <info@awaresystems.be>; Mon, 23 Jan 2012 15:29:14 +0100 (CET)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0-rc2
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144])
	by mx-k.one.com (Postfix) with ESMTP id 58F64FC2D8
	for <info@awaresystems.be>; Mon, 23 Jan 2012 14:29:14 +0000 (UTC)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id 852591ED9FB;
	Mon, 23 Jan 2012 09:27:55 -0500 (EST)
Received: from mail.sidefx.com (mail.sidefx.com [38.99.137.163])
	by lists.maptools.org (Postfix) with ESMTPS id 01FF51ED9FB
	for <tiff@lists.maptools.org>; Mon, 23 Jan 2012 09:04:30 -0500 (EST)
Message-ID: <4F1D68EC.9080403@sidefx.com>
X-DKIM: Sendmail DKIM Filter v2.8.2 mail.sidefx.com 14CF15D324
Date: Mon, 23 Jan 2012 09:04:28 -0500
From: Edward Lam <edward@sidefx.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Tiff List <tiff@lists.maptools.org>
References: <4F1C3F22.1050401@ql.org>
	<alpine.GSO.2.01.1201221350510.15666@freddy.simplesystems.org>
	<alpine.GSO.2.01.1201221435500.15666@freddy.simplesystems.org>
	<4F1CBC56.2010909@ql.org> <2370.1327296253@sss.pgh.pa.us>
In-Reply-To: <2370.1327296253@sss.pgh.pa.us>
Subject: Re: [Tiff] update on tiff 4.x in debian
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

It's been awhile but since the last time I looked, the libtiff soname's 
were different by default. Have we fixed this in the default libtiff 
build yet?

ie. that "libtiff.so.<N>" has a default <N> value that is the same 
across major Linux distributions to mean the same major version of libtiff.

Thanks,
-Edward

On 23/01/2012 12:24 AM, Tom Lane wrote:
> Jay Berkenbilt<ejb@ql.org>  writes:
>> Thanks so much for getting on this.  I wish it had been on my radar
>> prior to 4.0.0 too.  Anyway, debian doesn't have 4.0.0 in unstable yet,
>> and it doesn't matter whether we break compatibility with what's in
>> experimental.  I'd be really surprised if Fedora has it either.
>
> Nope, Fedora does not have it yet.  My plan is to wait for the F-18
> cycle to begin, not so much because of libtiff itself as because I
> figure I already caused enough trouble in F-17 with bumping libpng.
> So from the Red Hat end of things, incompatible changes in 4.0.1
> are fine.  I'd like it to happen within a couple of months though...
>
> 			regards, tom lane
> _______________________________________________
> Tiff mailing list: Tiff@lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/tiff
> http://www.remotesensing.org/libtiff/

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
