From owner-freebsd-ports@FreeBSD.ORG Fri Oct 21 22:39:59 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 59CEA16A41F for ; Fri, 21 Oct 2005 22:39:59 +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 1549F43D45 for ; Fri, 21 Oct 2005 22:39:59 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 8D239301A; Fri, 21 Oct 2005 17:39:58 -0500 (CDT) Date: Fri, 21 Oct 2005 17:39:58 -0500 To: "Michael C. Shultz" Message-ID: <20051021223958.GA19955@soaustin.net> References: <43522953.6050700@ebs.gr> <200510211454.41789.ringworm01@gmail.com> <20051021220910.GA18988@soaustin.net> <200510211519.47370.ringworm01@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200510211519.47370.ringworm01@gmail.com> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: freebsd-ports@freebsd.org 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 22:39:59 -0000 On Fri, Oct 21, 2005 at 03:19:47PM -0700, Michael C. Shultz wrote: > Seems like the quantity of ports available will eventually hit a plateau > with the current two level directory structure. No one is afraid to update > the basic OS when its needed, even when it means using an entirly different > file system ( ie. UFS1 -=> 2 ), why be so scared when it comes to the ports > system? Then PLEASE SUBMIT PATCHES. Tested ones. Involving portsmon. Involving the build cluster. Involving marcusom tinderbox. Involving FreshPorts. Involving everything in bsd.*.mk. Involving fixing up all the dependencies after all the thousands of repocopies. You will be submitting thousands, if not tens of thousands, of lines of patches to do so, invoving sh, awk, sed, perl, python, and SQL -- that I know of. There are probably others. Now: I am not going to discuss this issue any further until I see those patches. People, you just have No Idea how much work you are talking about here, just to fiddle around with organizing ports into directories on a physical disk, which I will continue to restate my opinion until I am blue in the face that is the wrong problem to solve _anyway_. The _right_ problems to solve are searching and browsing. If you solve those problems correctly, the physical layout on disk becomes hidden as an implementation detail and no one but hardcore ports developers ever has to think about it again. And you don't have to regression test thousands of lines of patches to do so. This is at least the 20th time this particular idea has been floated. It hasn't gotten any better the last 19 times. Please go back and read the archives. I'm done discussing it. mcl