From owner-freebsd-ports@FreeBSD.ORG Fri Oct 21 23:29:33 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19F9C16A420 for ; Fri, 21 Oct 2005 23:29:33 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dukecmmtao02.coxmail.com (dukecmmtao02.coxmail.com [68.99.120.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D1BA43D48 for ; Fri, 21 Oct 2005 23:29:32 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by dukecmmtao02.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051021232937.LSPR7750.dukecmmtao02.coxmail.com@dns1>; Fri, 21 Oct 2005 19:29:37 -0400 From: Vizion To: freebsd-ports@freebsd.org Date: Fri, 21 Oct 2005 16:24:21 -0700 User-Agent: KMail/1.8 References: <43522953.6050700@ebs.gr> <200510211454.41789.ringworm01@gmail.com> <20051021220910.GA18988@soaustin.net> In-Reply-To: <20051021220910.GA18988@soaustin.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510211624.24001.vizion@vizion.occoxmail.com> Cc: Mark Linimon Subject: Re: [SUGGEST] Reform eclipse and eclipse related ports 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: Fri, 21 Oct 2005 23:29:33 -0000 On Friday 21 October 2005 15:09, the author Mark Linimon contributed to the dialogue on- Re: [SUGGEST] Reform eclipse and eclipse related ports: >On Fri, Oct 21, 2005 at 02:54:41PM -0700, Michael C. Shultz wrote: >> My .02 cents worth - - - Would the ports system handle adding another >> level to its directory structure? > >This is the biggest FAQ about the ports collection and the answer is >always going to be the same: NO. We have nearly ten thousand lines of >automated tools which have the two-level assumption hardwired into them. >Fixing this would require many, many, hundreds of hours to do the necessary >rewriting and regression testing. > >Reading back through the mailing lists would have shown you this. Maybe the hard lesson from this is that before coding any future project for freebsd the proposed structure and a block diagram could be: 1. passed to a systems engineer to advise on the structure. That should avoid "hard-wired" design limitations in future projects. 2. Placed on the freebsd.org website for comunity input. Given that this is such an obvious design flaw why is their such reluctance to mitigate its effects by introducing additional categories! david -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit.