From owner-freebsd-ports@FreeBSD.ORG Mon May 7 20:06:36 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D99B816A402 for ; Mon, 7 May 2007 20:06:36 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmmtao106.cox.net (eastrmmtao106.cox.net [68.230.240.48]) by mx1.freebsd.org (Postfix) with ESMTP id 90C0913C45D for ; Mon, 7 May 2007 20:06:36 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmmtao106.cox.net (InterMail vM.7.05.02.00 201-2174-114-20060621) with ESMTP id <20070507200635.FEFJ12193.eastrmmtao106.cox.net@eastrmimpo02.cox.net>; Mon, 7 May 2007 16:06:35 -0400 Received: from mezz.mezzweb.com ([24.255.149.218]) by eastrmimpo02.cox.net with bizsmtp id wL6a1W00k4iy4EG0000000; Mon, 07 May 2007 16:06:35 -0400 Date: Mon, 07 May 2007 15:09:06 -0500 To: "Kris Kennaway" From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: <20070502193159.GB42482@xor.obsecurity.org> <463F7236.4080108@FreeBSD.org> <20070507184231.GA50639@xor.obsecurity.org> Content-Transfer-Encoding: Quoted-Printable Message-ID: In-Reply-To: <20070507184231.GA50639@xor.obsecurity.org> User-Agent: Opera Mail/9.20 (Linux) Cc: ports@freebsd.org, Doug Barton Subject: Re: HEADS UP: xorg upgrade plans X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2007 20:06:37 -0000 On Mon, 07 May 2007 13:42:31 -0500, Kris Kennaway = = wrote: > On Mon, May 07, 2007 at 11:38:46AM -0700, Doug Barton wrote: >> Kris Kennaway wrote: >> >Hi all, >> > >> >After many months of hard work (mostly by flz@, as well as others) w= e >> >are approaching readiness of the xorg 7.2 upgrade. Because this is = a >> >huge and disruptive change, we're going to approach it very carefull= y. >> >> Good news that this is moving forward! Congrats to all involved. >> >> >The current plan is the following: >> > >> >2) Final prep work in git repository. We need a day or two to confi= rm >> >the upgrade method for users. Unfortunately testing has exposed a >> >critical deficiency in portupgrade so 'portupgrade -a' will not be >> >enough to give a working upgrade, and some pre-upgrade steps will be= >> >required. >> >> Has portmaster been evaluated as an upgrade tool? I'm in a better >> position atm to be able to address any deficiencies if that will help= >> speed this along. My plan is to run 'portmaster -r pkg-config\*'. I think it should do fin= e = as 'portmaster -r' will do it in order very well. > No, at a minimum I am not comfortable recommending its use until it > saves old shared libraries across updates (I sent you email about this= > a while ago), which is a vital safety and robustness mechanism. I am one of people that dislike this and it is not required to get build= = function. ;-) I think this option should be disable by default, because = = put stuff in lib/compat/pkg hides the problems. Also: http://www.freebsd.org/gnome/docs/faq2.html#q2 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [...] Prevent two versions of the same library. A common source of build failures is the existence of multiple versions = of = the same library. This can happen if you have two different versions of = a = port installed, or can even happen through normal portupgrade use. You c= an = back up the libraries in /usr/local/lib/compat/pkg and remove them, and = = then run portupgrade -u -rf pkg-config. This will force a rebuild of all= = GNOME-related apps (and a fair number of other apps) without retaining o= ld = versions of libraries in /usr/local/lib/compat/pkg. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Cheers, Mezz >> >Also a post-upgrade step is required to deal with merging >> >remaining files from /usr/X11R6 into /usr/local. >> > >> >3) Once the proposed upgrade method is in place, we will publish a >> >tarball of the prepared ports tree and request that *all* our ports >> >developers test the upgrade on their own machines before it is >> >committed to CVS. There are many things that can go wrong and we ne= ed >> >to make sure that the upgrade goes as smoothly as possible for our >> >less technical users. In particular all ports committers are expect= ed >> >to participate in this process of eating our own dogfood :) >> >> Any updates on a timeline for this? > > Some time this week > >> >> >4) Once a suitable number of success reports (e.g. 50) are received >> >and all reported issues are resolved, we'll proceed with importing >> >into CVS. >> > >> >5) CVS will stay frozen for a period to be evaluated (probably anoth= er >> >couple of weeks) to deal with the inevitable remaining fallout as >> >users encounter yet more problems with the upgrade. >> >> Do you intend to keep the entire ports tree frozen for weeks? Perhaps= >> I misunderstand? > > Yes, that is the plan. This is an "all hands" event, and keeping it > frozen is the best way to focus developers onto those tasks. > > Kris -- = mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org http://wiki.freebsd.org/multimedia - multimedia@FreeBSD.org