From owner-freebsd-current@FreeBSD.ORG Sun Apr 4 12:11:38 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 EF90A106564A for ; Sun, 4 Apr 2010 12:11:38 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id 767A78FC0A for ; Sun, 4 Apr 2010 12:11:38 +0000 (UTC) Received: from p578b68b8.dip0.t-ipconnect.de ([87.139.104.184] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1NyOfw-00087v-39; Sun, 04 Apr 2010 14:11:36 +0200 Message-ID: <4BB881F4.1030405@gwdg.de> Date: Sun, 04 Apr 2010 14:11:32 +0200 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.1.9) Gecko/20100402 Thunderbird/3.0.4 MIME-Version: 1.0 To: Garrett Cooper References: <4BA7E0B8.3080406@delphij.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie 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 12:11:39 -0000 On 04.04.2010 13:24 (UTC+1), Garrett Cooper wrote: > On 3/26/10, Robert Watson wrote: >> 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. Older 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 the >> compatibility issues you describe. Perhaps you could clarify a bit the >> 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? It 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 do I have to expect unwanted side effects? Thanks, Rainer Hurling > 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...