From owner-freebsd-questions@FreeBSD.ORG Sat Jun 25 18:25:16 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99A7D16A41C; Sat, 25 Jun 2005 18:25:16 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 736D943D1F; Sat, 25 Jun 2005 18:25:16 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id DAF89A19; Sat, 25 Jun 2005 13:25:14 -0500 (CDT) Date: Sat, 25 Jun 2005 13:25:14 -0500 To: Ted Mittelstaedt Message-ID: <20050625182514.GA635@soaustin.net> References: <200506242117.29688.shinjii@virusinfo.rdksupportinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: Daniel O'Connor , freebsd-stable@freebsd.org, Warren , freebsd-questions@freebsd.org Subject: Re: Portupgrade in Xfree86 pkg failed 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: Sat, 25 Jun 2005 18:25:16 -0000 On Sat, Jun 25, 2005 at 09:14:26AM -0700, Ted Mittelstaedt wrote: > Why are you building xfree86? FreeBSD 5.4 uses Xorg. It's > just about the same code just different licensing. I don't think the > FreeBSD core is bothering to keep the xfree86 port working on FreeBSD 5.X > just FreeBSD 4.11 I'm sorry, but this is wrong on almost all counts. The default X server that is installed by the base for 5.4 is indeed xorg, but both XFree and xorg are being actively maintained. A great deal of work goes into keeping both X servers working on the active source branches. As for the licensing meta-fiasco, see the FAQ or use Google to find out more; this has been hashed and re-hashed and re-re-hashed here, and in other venues, many times. mcl