From owner-freebsd-current@FreeBSD.ORG Thu Nov 2 16:50:59 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 056BA16A415; Thu, 2 Nov 2006 16:50:59 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk.360sip.com [72.236.70.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id E345143D78; Thu, 2 Nov 2006 16:50:48 +0000 (GMT) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.47] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.6) with ESMTP id kA2GofiV008479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Nov 2006 08:50:42 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <454A21DB.8060908@FreeBSD.org> Date: Thu, 02 Nov 2006 08:50:35 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Ruslan Ermilov References: <454936CA.6060308@FreeBSD.org> <20061102115058.GB10961@rambler-co.ru> In-Reply-To: <20061102115058.GB10961@rambler-co.ru> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: "current@freebsd.org" , julian@elischer.org Subject: Re: libpthread shared library version number 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: Thu, 02 Nov 2006 16:50:59 -0000 Ruslan Ermilov wrote: > On Wed, Nov 01, 2006 at 04:07:38PM -0800, Maxim Sobolev wrote: >> Guys, >> >> I have noticed that libpthread shared library version number in 6-STABLE >> and 7-CURRENT is the same (.2), which causes all threaded application >> compiled for 6-STABLE to segfault when executed on 7-CURRENT system, >> unless libpthread.so.2 is replaced with with its 6-STABLE version which >> in turn will create problems with threaded apps compiled for 7-CURRENT. >> IMHO we should increase version number in 7-CURRENT, so that it is in >> the line of what we have for other system libraries. >> >> Any objections? >> > Last time we bumped them was right before 6.0-RELEASE; we did it > both in HEAD and RELENG_6. We certainly should be bumping them > all again closer to a 7.0-RELEASE, when the RELENG_7 is about to > be created. If we bump some majors now, and break APIs later but > still before a release (we are allowed to do it in -CURRENT), we > would have to bump them again before a release, and because it's > probably hard to track all changes we will unconditionally bump > them all before a RELENG_7 is created. I don't understand that part. We don't support binary compatibility with binaries compiled for -CURRENT or pre-release libraries, do we? Bumping it now would allow using 6-STABLE binaries on -CURRENT, which is my main point here. If we ever break ABI in -CURRENT later on not a big deal, because no vendor should compile its production binaries for -CURRENT anyway. -Maxim