From owner-freebsd-ports@FreeBSD.ORG Sun Feb 1 22:32:06 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3D46106564A for ; Sun, 1 Feb 2009 22:32:06 +0000 (UTC) (envelope-from vehemens@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.freebsd.org (Postfix) with ESMTP id C3C088FC0C for ; Sun, 1 Feb 2009 22:32:06 +0000 (UTC) (envelope-from vehemens@verizon.net) Received: from sam ([71.107.13.206]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0KEE00GIYRX7VHQ1@vms046.mailsrvcs.net> for freebsd-ports@freebsd.org; Sun, 01 Feb 2009 16:31:56 -0600 (CST) Date: Sun, 01 Feb 2009 14:36:04 -0800 From: vehemens In-reply-to: To: Alex Goncharov Message-id: <200902011436.04366.vehemens@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200901311153.58361.vehemens@verizon.net> <200902011034.50759.vehemens@verizon.net> User-Agent: KMail/1.9.10 Cc: freebsd-ports@freebsd.org, alex-goncharov@comcast.net Subject: Re: Unhappy Xorg upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2009 22:32:07 -0000 On Sunday 01 February 2009 11:22:52 am Alex Goncharov wrote: > | This has nothing to do with Linux. The issue is that that while src > | has a stable versus current branch, there is no stable branch for > | ports. The result is major updates are almost always problematic. > > Any data points to support the last statement? How about the last two xorg updates. Gnome has similar problems. > | You wouldn't be able to keep other updates unless you manully patched the > | tree, but you would be able to use the system until it's fixed. > > What the ETA for the new X fix? Not a clue. > | > You may assume that X is going to be fixed -- but what if not, in, say > | > a year? > | > | Your kidding me right?? > > No. You *know* that it is going to be fixed in a year? If yes, > what's the source of your knowledge? What resources are going to be > dedicated to work on my three problems? Not a clue. > | > | Well, it depends on which ports you are updating. > | > > | > All. > | > | Your saying that you build every port including the language options and > | never had a problem in the last 18 months until the xorg update ?!?!? > > Yes, I am saying exactly this. I happen not to run Gnome or KDE. > > | > | If you only run X, then I would expect your statement to be correct. > | > > | > Not sure what you mean here: nobody "runs only X". It's impossible. > | > | To be precise, it's the xorg port. So yes it's possible. > > Hm, let's see: > > ---------------------------------------- > Information for xorg-server-1.5.3_2,1: > > Depends on: ([ I exclude the "X things" ]): > Dependency: expat-2.0.1 > Dependency: openssl-0.9.8j > Dependency: pciids-20081012 > Dependency: e2fsprogs-libuuid-1.41.3_1 > Dependency: python25-2.5.2_3 > Dependency: pkg-config-0.23_1 > Dependency: libpthread-stubs-0.1 > Dependency: libiconv-1.11_1 > Dependency: gettext-0.17_1 > ---------------------------------------- > > Plenty of non-xorg things are needed for xorg, right? > > And if I build from the sources, I also need gmake, bison, autoconf > etc. Your kidding me again right??