From owner-freebsd-ports@FreeBSD.ORG  Sun Nov 30 18:10:38 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B378016A4CE
	for <freebsd-ports@freebsd.org>; Sun, 30 Nov 2003 18:10:38 -0800 (PST)
Received: from gabby.gsicomp.on.ca
	(CPE00062566c7bb-CM000039c69a66.cpe.net.cable.rogers.com [24.192.222.167])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4938B43FDD
	for <freebsd-ports@freebsd.org>;
	Sun, 30 Nov 2003 18:10:35 -0800 (PST)
	(envelope-from matt@gsicomp.on.ca)
Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18])
	by gabby.gsicomp.on.ca (8.12.9p2/8.12.9) with SMTP id hB11wT1Z025557;
	Sun, 30 Nov 2003 20:58:29 -0500 (EST)
	(envelope-from matt@gsicomp.on.ca)
Message-ID: <001501c3b7af$b5e465b0$1200a8c0@gsicomp.on.ca>
From: "Matthew Emmerton" <matt@gsicomp.on.ca>
To: <freebsd-ports@freebsd.org>,
	"Matthias Andree" <ma@dt.e-technik.uni-dortmund.de>
References: <m3vfp1miem.fsf@merlin.emma.line.org>
Date: Sun, 30 Nov 2003 21:06:19 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: Re: Why does ldconfig insist on a trailing number?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2003 02:10:38 -0000

> ldconfig is documented as only looking at files that have some version
> number after the .so suffix, say, .so.4. This looks rather ugly when the
> library version is part of the name, as in BerkeleyDB ports.
>
> Is there a functional requirement for the trailing version number?  If
> so, what is it?

I would imagine that the trailing number is the version number.  If the
BerkeleyDB ports were taking full advantage of the versioning ability
supplied by ldconfig, they would have called their libraries libdb.so.2,
libdb.so.3 and libdb.so.4 instead of libdb2.so.0, libdb3.so.0, libdb4.so.0.

One might claim that the libraries need to be called different things due to
API changes, but generally, API changes happen on major number boundaries so
the verion number handles this.

--
Matt Emmerton