From owner-freebsd-current@FreeBSD.ORG Sun Apr 4 20:42:28 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CCF21065674 for ; Sun, 4 Apr 2010 20:42:28 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f195.google.com (mail-qy0-f195.google.com [209.85.221.195]) by mx1.freebsd.org (Postfix) with ESMTP id E6F648FC0A for ; Sun, 4 Apr 2010 20:42:27 +0000 (UTC) Received: by qyk33 with SMTP id 33so3614622qyk.28 for ; Sun, 04 Apr 2010 13:42:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=v8AGsm9j43wLczM9wrkkMPOJo/pOoJ4ySr7So5rU1Ps=; b=YvLSwWJv08gSbQfP4JC9D1TUUlN2PPjm1a6jRRSZWUXLtrfATcTJ/4gD1TZmcOM3cH PDje3ft/gkAdUQd23Pq2J2qXm5Pd9jTY72JcJJROVJVGOVVXD94Sz6CpAh2eBwFzW97O Ax4ytEY2pu4jLDMH0rUq2ZTXG0Ek02x4SzAYk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qD9kRbzNtaCd3w2/SkUJ14Xgyq+Mq7nsgT9eiRdXXa0dvoQ1ARR1iZghIWapblWKZC clFjNiBecSisPMjiVaXmT18V1cdI46DugkHetd40SWjnN60FDmRxbdcr9S5ZMbL6naMC jMFAlDRgtn3FZ4zzFroHobisnsDq4QWDp8Wu4= MIME-Version: 1.0 Received: by 10.229.33.72 with HTTP; Sun, 4 Apr 2010 13:42:26 -0700 (PDT) In-Reply-To: <4BB881F4.1030405@gwdg.de> References: <4BA7E0B8.3080406@delphij.net> <4BB881F4.1030405@gwdg.de> Date: Sun, 4 Apr 2010 13:42:26 -0700 Received: by 10.229.241.66 with SMTP id ld2mr7733419qcb.78.1270413746334; Sun, 04 Apr 2010 13:42:26 -0700 (PDT) Message-ID: From: Garrett Cooper To: Rainer Hurling Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys] 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: Sun, 04 Apr 2010 20:42:28 -0000 On Sun, Apr 4, 2010 at 5:11 AM, Rainer Hurling wrote: > On 04.04.2010 13:24 (UTC+1), Garrett Cooper wrote: >> >> On 3/26/10, Robert Watson =A0wrote: >>> >>> On Mon, 22 Mar 2010, Xin LI wrote: >>> >>>> A MFC of this update is planned, but we will have to make some rather >>>> aggressive changes against the library and more testing. >>>> >>>> Please make sure that you have at least libxml2-2.7.6_2 in your ports >>>> tree >>>> >>>> before even thinking about updating your ports tree. =A0Older libxml2 = uses >>>> some knowledge of zlib internals that has been changed in this update >>>> which >>>> is known to cause problem. >>> >>> While the update sounds like a good idea (as does moving to symbol >>> verisoning >>> for this library), I'm not yet convinced an MFC is a good idea given th= e >>> compatibility issues you describe. =A0Perhaps you could clarify a bit t= he >>> failure mode: this affects only people who rebuild their ports using >>> exactly >>> the same ports versions, but after having done an upgrade that includes >>> this >>> update? =A0It sounds like existing binaries will continue to work since >>> they >>> will reference the old library version? >> >> Yes, but the number of libraries which need to be fixed is a pain. If >> you go the conservative (not ultra conservative) route, you'll have to >> rebuild all dependencies of graphics/png and graphics/tiff (which >> includes a ton of gnome apps, X, etc). Oh, and did I forget to mention >> that libtool hardcodes paths and versioning information? Of course >> most people won't see this fact until they run make delete-old-libs, >> but it's a doosy... This is the primary reason why Gentoo Linux has a >> script to clean up these [libtool] messes... > > To avoid the biggest trouble when updating I temporarily went another way= . > Before 'make delete-old-libs' I made a copy of libz.so.5 under compat: > > cp -p /lib/libz.so.5 /usr/local/lib/compat/ > cp -p /usr/lib32/libz.so.5 /usr/local/lib32/compat/ > > I plan to delete these copies in some weeks. Do you think this is ok or d= o I > have to expect unwanted side effects? I'm pretty sure that works as well (just make sure to rerun ldconfig and ldconfig -32 after the fact -- or do /etc/rc.d/ldconfig restart, boot your system into multiuser mode, etc, and you should be in good shape); it should get you past this transition. It would be nice if there an entry in UPDATING added for this to warn people of the breakage and this potential suggested workaround *HINT*... >> That point alone is a reason for being ultra-conservative with this >> MFCing change. This won't affect folks building from scratch after >> this commit, but it'll easily kill off an afternoon or day for folks >> upgrading if they one isn't careful because the impact is large. >> >> Of course scripting the activity to avoid these times of base system >> library bumps is trivial, but my script that I whipped up still has >> rough edges and I'd rather not submit it quite yet... Thanks, -Garrett