From owner-freebsd-current@FreeBSD.ORG Mon May 22 02:08:16 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEDC716A42F; Mon, 22 May 2006 02:08:16 +0000 (UTC) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 769F543D45; Mon, 22 May 2006 02:08:16 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [192.168.2.2]) ([10.251.60.93]) by a50.ironport.com with ESMTP; 21 May 2006 19:08:16 -0700 Message-ID: <44711D0F.3060104@elischer.org> Date: Sun, 21 May 2006 19:08:15 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: <4470DB4A.6020304@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: re@freebsd.org, Hajimu UMEMOTO , current@freebsd.org Subject: Re: Shared library version bump? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 02:08:17 -0000 Daniel Eischen wrote: > On Sun, 21 May 2006, Julian Elischer wrote: > >> Hajimu UMEMOTO wrote: >> >>> deischen> Go ahead. Just realize though, that after 7.0 is released >>> deischen> you will have to support any ABI from then on without version >>> deischen> bumps (meaning, you have to keep shims for any old 7.0+ ABIs >>> deischen> in libc). >>> >>> ume> Okay, I'll do. >>> >> >> I assume htat EVENTUALLY we will bump numbers again when something >> sufficiently >> big needs to be done to the ABI. > > > Symbol versioning is suppose to allow one library to support different > ABIs, so the hope is that we will never have to bump libc's version > number. If you change ABI, you still have to keep the old code around > (or some sort of compatability shims) in the library. > yes but that could get too big a drain on resources oftetr while (trying ot shim really old stuff into really new stuff.) It might eventually get to a point where it would be good to cut and run..