From owner-freebsd-current Sat Sep 19 18:34:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05345 for freebsd-current-outgoing; Sat, 19 Sep 1998 18:34:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05306 for ; Sat, 19 Sep 1998 18:34:31 -0700 (PDT) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id NAA28202; Sun, 20 Sep 1998 13:34:02 +1200 (NZST) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id NAA09136; Sun, 20 Sep 1998 13:34:02 +1200 (NZST) Message-ID: <19980920133401.B9101@clear.co.nz> Date: Sun, 20 Sep 1998 13:34:01 +1200 From: Joe Abley To: Mark Huizer , freebsd-current@FreeBSD.ORG Subject: Re: ELF ldconfig References: <19980920042741.A6144@clear.co.nz> <199809192032.NAA02450@austin.polstra.com> <19980920013633.A425@xaa.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19980920013633.A425@xaa.iae.nl>; from Mark Huizer on Sun, Sep 20, 1998 at 01:36:33AM +0200 X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 20, 1998 at 01:36:33AM +0200, Mark Huizer wrote: > > See the conversion guidelines for more details: > > > > http://www.freebsd.org/~asami/elf-guidelines.txt > > Well, I started looking for it alright, but it seems a bit rude to me to > just make it libslang.1, and considering that the libslang makefile is > talking about elf major and minor version numbers, I got confused a > little :-) does elf except only major, or is that a FreeBSD specific > thing, or what? And why doesn't it matter when versions get upgraded and > all? That was my concern. Surely there must come a time when two versions of a shared library exist (with identical major version numbers), and an application requires to be dynamically linked to the older of the two because of some incompatability with the newer library? Assuming there is a good reason to use a single (major) version number in the naming scheme, there is a fair bit of work to do to update (a) every port that builds a shared object (149 of them), and (b) every port that depends on a shared library being installed (318 of them)... Those ports maintainers better get cracking :) > Mark Joe -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Net http://www.clear.net.nz/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message