From owner-freebsd-current@FreeBSD.ORG Thu Nov 2 11: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 CA12316A4C8; Thu, 2 Nov 2006 11:50:59 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49CE543D5C; Thu, 2 Nov 2006 11:50:58 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 018DA5E6A; Thu, 2 Nov 2006 14:50:57 +0300 (MSK) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id D353D5E5C; Thu, 2 Nov 2006 14:50:56 +0300 (MSK) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id kA2BowKT018036; Thu, 2 Nov 2006 14:50:58 +0300 (MSK) (envelope-from ru) Date: Thu, 2 Nov 2006 14:50:58 +0300 From: Ruslan Ermilov To: Maxim Sobolev Message-ID: <20061102115058.GB10961@rambler-co.ru> References: <454936CA.6060308@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LpQ9ahxlCli8rRTG" Content-Disposition: inline In-Reply-To: <454936CA.6060308@FreeBSD.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found 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 11:50:59 -0000 --LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 01, 2006 at 04:07:38PM -0800, Maxim Sobolev wrote: > Guys, >=20 > 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=20 > the line of what we have for other system libraries. >=20 > Any objections? >=20 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'm not sure if bumping them now and having a gap later is a good or bad idea; just some point to consider. There is another options: having a build knob that will bump all shlib majors for those -CURRENT users that need it *right now*. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --LpQ9ahxlCli8rRTG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFSduiqRfpzJluFF4RAlrUAJ9jXGjWlnEXUoCLdtAwPQ9AJsocdACbBw9h eFuUWMAi3CWjNOmSjg2WQQ8= =Dxwf -----END PGP SIGNATURE----- --LpQ9ahxlCli8rRTG--