Date: Thu, 2 Nov 2006 08:25:37 -0500 (EST) From: Daniel Eischen <deischen@freebsd.org> To: Ruslan Ermilov <ru@freebsd.org> Cc: "current@freebsd.org" <current@freebsd.org>, julian@elischer.org Subject: Re: libpthread shared library version number Message-ID: <Pine.GSO.4.64.0611020824150.12236@sea.ntplx.net> In-Reply-To: <20061102115058.GB10961@rambler-co.ru> References: <454936CA.6060308@FreeBSD.org> <20061102115058.GB10961@rambler-co.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2 Nov 2006, 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 No, in -current we force people to recompile everything. Plus we have symbol versioning in the libraries most likely to be effected. If we bump, we should enable symbol versioning at the same time. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0611020824150.12236>