From owner-freebsd-questions@FreeBSD.ORG Tue May 16 01:20:03 2006 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 E6A8E16A7A2 for ; Tue, 16 May 2006 01:20:03 +0000 (UTC) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (gw-ipinc.museum.rain.com [65.75.192.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6688743D45 for ; Tue, 16 May 2006 01:20:03 +0000 (GMT) (envelope-from james_mapson@umpquanet.com) Received: from ns.museum.rain.com (localhost [127.0.0.1]) by ns.museum.rain.com (8.13.4/8.13.4) with ESMTP id k4G1Jtau042713 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Mon, 15 May 2006 18:19:57 -0700 (PDT) (envelope-from james@umpquanet.com) Received: (from james@localhost) by ns.museum.rain.com (8.13.4/8.13.4/Submit) id k4G1Jsn3042712; Mon, 15 May 2006 18:19:54 -0700 (PDT) (envelope-from james) Date: Mon, 15 May 2006 18:19:54 -0700 From: James Long To: freebsd-questions@freebsd.org, fbsd Message-ID: <20060516011954.GA38831@ns.museum.rain.com> References: <20060514000623.339E216A491@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060514000623.339E216A491@hub.freebsd.org> User-Agent: Mutt/1.5.11 X-Greylist: Sender is SPF-compliant, not delayed by milter-greylist-2.0.2 (ns.museum.rain.com [127.0.0.1]); Mon, 15 May 2006 18:19:58 -0700 (PDT) Cc: Subject: Re: Has the port collection become to large to handle. 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: Tue, 16 May 2006 01:20:04 -0000 > Date: Sat, 13 May 2006 14:28:49 -0400 > From: "fbsd" > Subject: Has the port collection become to large to handle. > To: "freebsd-questions@FreeBSD. ORG" > Cc: ports@freebsd.org > > I for one think the port/package collection has already grown to > large to handle in it's present state. > Users are consuming massive bandwidth to download and it > consumes a very large chunk of disk space. Saying nothing about > the wasted resources consumed to back it up repeatedly. What's your domain name again? cvsup downloads only the bits of the port tree that have changed. An intelligent backup strategy backs up the entire tree infrequently, and the rest of the time, backs up only the files that have changed. And since the ports tree is readily available off the net, why back it up at all? > This problem is caused by there being no mandatory requirement There is no mandatory requirement on anyone to do anything. > So my question is how do we users make our needs known > to the ports maintainer group so that will seriously address > the problem of the packages being outdated? I suggest you purchase one or more high-powered build machines and ship them prepaid to the ports maintainer. Repeat every eight or ten months to ensure that the build machines remain state-of-the-art.