From owner-freebsd-x11@FreeBSD.ORG Thu Dec 23 05:43:17 2004 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC9BC16A4CE for ; Thu, 23 Dec 2004 05:43:17 +0000 (GMT) Received: from niobe.ijs.si (mail.ijs.si [193.2.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC82443D39 for ; Thu, 23 Dec 2004 05:43:16 +0000 (GMT) (envelope-from dejan.lesjak@ijs.si) Received: from localhost (localhost.ijs.si [127.0.0.1]) by niobe.ijs.si (Postfix) with ESMTP id 6ACCA21886A; Thu, 23 Dec 2004 06:43:15 +0100 (CET) Received: from niobe.ijs.si ([127.0.0.1]) by localhost (niobe.ijs.si [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08710-01; Thu, 23 Dec 2004 06:42:49 +0100 (CET) Received: from metatron.ijs.si (metatron.ijs.si [193.2.4.152]) by niobe.ijs.si (Postfix) with ESMTP id CB345218857; Thu, 23 Dec 2004 06:42:48 +0100 (CET) Received: from rincewind.ijs.si (rincewind.ijs.si [193.2.4.137]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by metatron.ijs.si (Postfix) with ESMTP id 8AD0A1C00722; Thu, 23 Dec 2004 06:42:48 +0100 (CET) From: Dejan Lesjak To: Kris Kennaway Date: Thu, 23 Dec 2004 06:42:47 +0100 User-Agent: KMail/1.7.2 References: <20041221193116.GA64452@xor.obsecurity.org> <200412220235.42655.dejan.lesjak@ijs.si> <20041222200325.GA53171@xor.obsecurity.org> In-Reply-To: <20041222200325.GA53171@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412230642.48135.dejan.lesjak@ijs.si> X-Virus-Scanned: amavisd-new at ijs.si cc: freebsd-x11@freebsd.org Subject: Re: [ports-i386@FreeBSD.org: yammi-1.0.r1_3 failed on i386 5-exp] X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 05:43:17 -0000 On Wednesday 22 of December 2004 21:03, Kris Kennaway wrote: > On Wed, Dec 22, 2004 at 02:35:42AM +0100, Dejan Lesjak wrote: > > On Wednesday 22 of December 2004 02:27, Kris Kennaway wrote: > > > On Tue, Dec 21, 2004 at 08:41:42PM +0100, Dejan Lesjak wrote: > > > > On Tuesday 21 of December 2004 20:31, Kris Kennaway wrote: > > > > > xorg fallout > > > > > > > > Yes, this one was expected, waiting for feedback from maintainer > > > > about PR 75079, which upgrades yammi and also fixes this problem (but > > > > unfortunately breaks yammi on 4.X). > > > > > > Since our immediate focus is on 4.x, I'd suggest marking this port > > > BROKEN if X_WINDOW_SYSTEM=xorg and leaving it for now (commit with > > > portmgr approval if you like). > > > > > > Kris > > > > The trouble with upgraded port in PR is rather with gcc on 4.x (or the > > way g++ includes behave) as far as I understand. But it is on my thoughts > > and if I don't hear from maintainer, I'll try if the fix (or rather a > > hint to what might be fix) i gave in PR works on 4.X (I only tested if it > > compiles), and either commit that or mark the port broken on 4.X before > > the 30th. > > The reason I suggested leaving it broken with xorg but working on 4.x > is so that any hypothetical users of 4.11-RELEASE can use the port. > But, it's probably not a big deal, and the maintainer doesn't appear > to be too interested in this problem. He's probably on vacation :) Nevertheless I've tried the proposed fix in PR and it seems to work on 4.X so I've commited it. The point is that this port as it was (or many of the fallouts for that matter were not broken with xorg, but rather with cleanup of dependency - removal of run depends on imake, which would be broken the same with XFree86-4 ports, so marking it broken with xorg wouldn't help. Upgrade in PR from maintainer already fixed this problem, unfortunately it broke build on 4.X and that is why I waited a bit. > I think the only remaining nit is the missing file from the dri > pkg-plist which turned up on the pointyhat build. Apart from that, > you're good to go! > > Kris Anholt fixed that and all this stuff should finally be commited now, I think we got everything :-) Thank you for all the work with this. Pointyhat and dosirak are really great assets to have :-) Dejan