From owner-freebsd-hackers Thu Oct 1 10:51:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29400 for freebsd-hackers-outgoing; Thu, 1 Oct 1998 10:51:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29394 for ; Thu, 1 Oct 1998 10:51:15 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id KAA09819; Thu, 1 Oct 1998 10:50:44 -0700 (PDT) Date: Thu, 1 Oct 1998 10:50:44 -0700 (PDT) From: Alex To: "Kaleb S. KEITHLEY" cc: devel@XFree86.org, hackers@FreeBSD.ORG Subject: Re: ELF shared library "revision" numbers In-Reply-To: <36139828.2F3833FD@ics.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Oct 1998, Kaleb S. KEITHLEY wrote: > > It doesn't follow your "Unless the ABI changes in an incompatible way, > > you don't change the SONAME" statement above for your definition of > > "incompatible". > > That's the ELF definition of incompatible, not mine. > > > The definition of "incompatible" that FreeBSD has chosen > > includes adding new functions while keeping all the previous interfaces > > unchanged. > > Ugh. That's bad. That's going to force people to keep old libraries > around for old programs, and /usr/lib is going to suffer from bloat. > Either that or it's going to force people to go manually dink their > /usr/lib to create symlinks if they want to get rid of old libraries. > (Yeah, yeah, disk is cheap.) It's _good_. It would force people to link statically if they're horribly desperate, or perhaps just relink. Yes, it's true Linux added new functions to its libc5 without bumping the major number. Let me tell you, when you've got a populace that's so full of clueless idiots, doing something like that is a bad idea. Ever try and run programs linked with libc.so.5.44 on a libc.so.5.12 system? It's not fun, but something like that _should_ work. When you introduce binary or source incompatablity, it's time to change the major number. > Bumping the SONAME/version when you add APIs doesn't buy you anything. It buys you sanity. Unless you want to explain why a libc.so.3 from the 12th won't work with programs linked with a libc.so.3 from the 13th. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message