From owner-freebsd-current@FreeBSD.ORG Fri Mar 26 11:33:35 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 1C4FA1065701 for ; Fri, 26 Mar 2010 11:33:35 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id EC0128FC19 for ; Fri, 26 Mar 2010 11:33:34 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 797F246B64; Fri, 26 Mar 2010 07:33:34 -0400 (EDT) Date: Fri, 26 Mar 2010 11:33:34 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: d@delphij.net In-Reply-To: <4BA7E0B8.3080406@delphij.net> Message-ID: References: <4BA7E0B8.3080406@delphij.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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: Fri, 26 Mar 2010 11:33:35 -0000 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? Robert N M Watson Computer Laboratory University of Cambridge