From owner-freebsd-current@FreeBSD.ORG Thu Nov 2 22:07:46 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 A63BB16A746; Thu, 2 Nov 2006 22:07:46 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D679B43D49; Thu, 2 Nov 2006 22:07:45 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id kA2M7i5J010319; Thu, 2 Nov 2006 17:07:44 -0500 (EST) Date: Thu, 2 Nov 2006 17:07:44 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Ruslan Ermilov In-Reply-To: <20061102214157.GC2028@rambler-co.ru> Message-ID: References: <454936CA.6060308@FreeBSD.org> <20061102115058.GB10961@rambler-co.ru> <20061102140948.GA70915@lor.one-eyed-alien.net> <20061102182419.GC774@rambler-co.ru> <454A60E9.7020303@FreeBSD.org> <20061102214157.GC2028@rambler-co.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-2.0.2 (mail.ntplx.net [204.213.176.10]); Thu, 02 Nov 2006 17:07:44 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: current@freebsd.org Subject: Re: libpthread shared library version number X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2006 22:07:46 -0000 On Fri, 3 Nov 2006, Ruslan Ermilov wrote: > On Thu, Nov 02, 2006 at 01:19:37PM -0800, Maxim Sobolev wrote: >> Ruslan Ermilov wrote: >>> On Thu, Nov 02, 2006 at 08:09:48AM -0600, Brooks Davis wrote: >>> Hmm, bumping not versioned libraries *now* and not bumping them >>> again at pre-release would work, but doing it without also bumping >>> "to be versioned" libraries is IMO pointless. And if we bump all >>> of them now, we'll have to bump some of them again when versioning >>> is turned on by default. >> >> No, we will not have to do it. Why would we? It's -CURRENT, so that >> nobody really cares about backward/forward compatibility within that branch. >> > I'd very much like NOT to have to recompile all of my installed > ports on my -CURRENT boxes the day we turn on symbol versioning, > and that will require the shlib major bump of those libs that > will provide symbol versioning. If we do the bump now, we'll > have to do it again later, and that's slightly against the rule > that we only bump them once inside a branch. No, we don't bump library versions more than once in -current in the same release cycle. Yes, sometimes this requires that you have to rebuild all your ports. And you can safely enable symbol versioning without bumping library versions -- libraries and binaries built against non-symbol-versioned libraries will run just fine on the same libraries with symbol versioning. The thing that won't work is trying to use libraries/binaries built against symbol versioned libraries on those same libraries _without_ symbol versioning. I hope you can follow what I am saying, because it sounds confusing even to me ;-) -- DE