Received: from [207.176.88.85] by phillip.cerious.com (NTMail 3.03.0017/7.aaxh) with ESMTP id pcrews for <pcrews@cerious.com>; Tue, 23 May 2000 10:03:51 -0400
Received: from localhost (daemon@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) with SMTP id JAA18746;
	Tue, 23 May 2000 09:24:04 -0400
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Tue, 23 May 2000 09:23:28 -0400
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) id JAA18696
	for tiff-outgoing; Tue, 23 May 2000 09:23:27 -0400
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15])
	by gate7.olympiakos.com (8.9.3/8.9.3) with ESMTP id JAA18693
	for <tiff@olympiakos.com>; Tue, 23 May 2000 09:23:24 -0400
Received: from home.com ([24.68.88.161]) by mail.rdc2.on.home.com
          (InterMail vM.4.01.02.17 201-229-119) with ESMTP
          id <20000523132316.PMYG23706.mail.rdc2.on.home.com@home.com>
          for <tiff@olympiakos.com>; Tue, 23 May 2000 06:23:16 -0700
Message-ID: <392A9495.C2A1CDCD@home.com>
Date: Tue, 23 May 2000 09:24:21 -0500
From: Frank Warmerdam <warmerda@home.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: TIFF Mailing List <tiff@olympiakos.com>
Subject: Re: SONAME=libtiff.so
References: <1000523090312.ZM28695@dsapp3.hmi.de> <392A7BF9.2D7A@srz-berlin.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-tiff@olympiakos.com

Helge Blischke wrote:
> 
> Thomas Anders wrote:
> >
> > Hello,
> >
> > the latest libtiff 3.5.5 distribution produces a libtiff.so with a
> > SONAME=libtiff.so. Is there any reason for not having proper version
> > numbers in the SONAME?

Thomas, 

There is no compelling reason that version numbers of some sort are not
included in libtiff; however, we have tried to avoid messing too much with
the dso generation.  If we rework libtiff to use autoconf we will also likely
switch to use automake, and libtool.  I imagine we would then use the normal
libtool .so numbering scheme (not directly related to release numbers like 
3.5.5 for reasons clarified in the libtool documentation).  However, this is
all a substantial effort to do well, and we aren't promising when it will 
happen. 

In the meantime of course, it is always possible to hack the makefiles a bit
locally to attach whatever your desired version numbers are.  Presumably this
is what Sun did. 

Best regards,

---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerda@home.com
light and sound - activate the windows | http://members.home.com/warmerda
and watch the world go round - Rush    | Geospatial Programmer for Rent
