From owner-freebsd-x11@FreeBSD.ORG Wed Mar 28 11:34:02 2007 Return-Path: X-Original-To: freebsd-x11@freebsd.org Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E752916A401; Wed, 28 Mar 2007 11:34:02 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id A463013C4BE; Wed, 28 Mar 2007 11:34:02 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id CC6432081; Wed, 28 Mar 2007 13:09:18 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 3D995207E; Wed, 28 Mar 2007 13:09:18 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id ECF26A1073; Wed, 28 Mar 2007 13:09:17 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Florent Thoumie References: <46022E59.7030407@jabbe.de> <46026D62.4010009@FreeBSD.org> Date: Wed, 28 Mar 2007 13:09:17 +0200 In-Reply-To: <46026D62.4010009@FreeBSD.org> (Florent Thoumie's message of "Thu, 22 Mar 2007 11:49:54 +0000") Message-ID: <861wj9sjz6.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-x11@freebsd.org Subject: Re: What can I do? X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2007 11:34:03 -0000 Florent Thoumie writes: > It's working for you without major breakage only because you're using > 500 ports out of 16000+ (like I do, like almost everybody does). Still > some ports are breaking with the new xorg, or because of the prefix > merge. We're working on those ports. Have a look at [1] or [2] to get > regular updates on xorg work. > [...] > As you can see on [3], we're still committing fixes. We usually fix > those ports by ourselves (miwi, lesi and myself) but occasionally > forward them to maintainers when we can't figure out what's wrong or > when it requires non-trivial fix. When we fixed all ports broken in a > single experimental pointyhat build, a new one is scheduled and then we > get new errorlogs, ... I suspect you're way past the point where new issues show up faster than you can fix them. The only way out of this tar pit is to merge everything into the ports tree so other port maintainers have a real incentive to help you out. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no