From owner-freebsd-x11@FreeBSD.ORG Fri Nov 27 23:00:47 2009 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D06A0106566C; Fri, 27 Nov 2009 23:00:47 +0000 (UTC) (envelope-from vehemens@verizon.net) Received: from vms173015pub.verizon.net (vms173015pub.verizon.net [206.46.173.15]) by mx1.freebsd.org (Postfix) with ESMTP id B09098FC16; Fri, 27 Nov 2009 23:00:47 +0000 (UTC) Received: from sam ([72.87.243.167]) by vms173015.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KTS00H5JIKS2PZ6@vms173015.mailsrvcs.net>; Fri, 27 Nov 2009 17:00:28 -0600 (CST) From: vehemens To: Peter Jeremy Date: Fri, 27 Nov 2009 16:01:47 -0800 User-Agent: KMail/1.9.10 References: <200911261455.40399.vehemens@verizon.net> <20091127205335.GB81095@server.vk2pj.dyndns.org> In-reply-to: <20091127205335.GB81095@server.vk2pj.dyndns.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline Message-id: <200911271601.47677.vehemens@verizon.net> Cc: freebsd-x11@freebsd.org Subject: Re: xorg ports roadmap? 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: Fri, 27 Nov 2009 23:00:47 -0000 On Friday 27 November 2009 12:53:35 Peter Jeremy wrote: > On 2009-Nov-26 14:55:40 -0800, vehemens wrote: > >If your having so many problems with these updates, why not just split > > ports into current and stable branches? > > This isn't as easy as it sounds because there are interactions between > so many different pieces. Back when X.org/XFree86 was a small number > of ports (basically server, libraries and base clients), it wouldn't > have been too hard. X.org now comprises something like 250 pieces > with not-very-well documented interactions. > > It might help if X.org could be cleanly split into client ports and > server ports but even that's not possible because they both depend > on a number of X-related libraries. The suggestion was to have the entire ports tree as both a current and stable branch, then using the same (similar?) rules as used for the source branches. A ports freeze would mean that changes to the stable branch would be limited, but work could still go on in the current branch. The MFC process could be semi-automated.