From owner-freebsd-questions@FreeBSD.ORG Sun May 20 18:52:12 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 09CB916A41F for ; Sun, 20 May 2007 18:52:12 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id EC98313C457 for ; Sun, 20 May 2007 18:52:11 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id EE99C1A3C1C; Sun, 20 May 2007 11:53:08 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 291D651406; Sun, 20 May 2007 14:52:11 -0400 (EDT) Date: Sun, 20 May 2007 14:52:11 -0400 From: Kris Kennaway To: "P.U.Kruppa" Message-ID: <20070520185211.GB41728@xor.obsecurity.org> References: <20070520123428.W19823@small> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070520123428.W19823@small> User-Agent: Mutt/1.4.2.2i Cc: freebsd-questions@freebsd.org Subject: Re: Future development of xorg port X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 18:52:12 -0000 On Sun, May 20, 2007 at 12:39:41PM +0200, P.U.Kruppa wrote: > Hi, > > since now we all did/are doing our monster xorg port upgrade, I > wonder how the future development of xorg is planned. > > - Will we permanently receive small upgrades of xorg modules by > tracking -STABLE ? > - Will there be kind of an xorg-devel port? > - Or do we wait for the next big complete upgrade to 7.3 ? In general the plan is to do something like option 3. xorg-devel will probably be too much work (need to fork an additional ~300 ports) and frequent small updates will introduce too much churn and introduce too many dependency problems. Kris