Subject: Re: NetBSD 2.0 release date
To: Eric Haszlakiewicz <email@example.com>
From: John Franklin <firstname.lastname@example.org>
Date: 12/08/2003 14:08:06
On Dec 8, 2003, at 1:28 PM, Eric Haszlakiewicz wrote:
> On Mon, Dec 08, 2003 at 01:02:20PM -0500, John Franklin wrote:
>> On the other host, foo is linked with libc.13 and libother.0
>> dependencies. Locally, the loader would try to load both libc.13 (to
>> satisfy the foo dependency) and libc.12 (to satisfy the libother.0
>> dependency.) Conflicting library versions, program doesn't load,=20
>> is returned. It's OK for the loader to say no.
> what would be really neat is if the ld.so would look for earlier=20=
> of libother.0 that has the matching dependency. If libother.0.2 is=20
> against libc.13, but libother.0.1 exists and is linked against=20
> libc.12, then
> program foo, linked against libother.0 and libc.12 should be able to=20=
> just fine using libother.0.1. _That_ would allow full backwards=20
> without bumping major versions.
Hmm... wouldn't want to take a minor number without the decision coming=20=
from the library developer. Can ELF handle a third version number as a=20=
build number? That is, libother.0.1.0 is linked against libc.12, and=20
libother.0.1.1 is linked against libc.13.
ICBM: 35=B043'56"N 78=B053'27"W