From owner-freebsd-stable@FreeBSD.ORG Fri Dec 24 06:43:34 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8974916A4CE for ; Fri, 24 Dec 2004 06:43:34 +0000 (GMT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E1F443D2D for ; Fri, 24 Dec 2004 06:43:34 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id A0A7914901; Fri, 24 Dec 2004 00:43:33 -0600 (CST) Date: Fri, 24 Dec 2004 00:43:33 -0600 (CST) From: Mark Linimon X-X-Sender: linimon@pancho To: "Michael C. Shultz" In-Reply-To: <200412232224.05536.ringworm@inbox.lv> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: portsdb and portupgrade causes errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 06:43:34 -0000 On Thu, 23 Dec 2004, Michael C. Shultz wrote: > Way back when, I used to get the INDEX when running cvsup unless > I put it in the refuse file. Of coarse it was old and useless so one was > better off building their own INDEX. So why cant we just receive the > INDEX like we used to, but unlike before, l have it updated as often as > is being done now? Because the way we used to do it required tremendous churn in the CVS repository. And it was _still_ out of date. The fact that you can't refuse it is a bug, and has been reported to jdp. In the meantime, a cron script that does something like a fetch and then a copy is your best bet. There's really quite a bit of email in the mailing list archives about why this was done. The short summary is that in the short run there is some pain but in the long run this is a win for the project, and the users. mcl