From owner-freebsd-ports Tue Oct 29 10:21:56 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA14775 for ports-outgoing; Tue, 29 Oct 1996 10:21:56 -0800 (PST) Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14768 for ; Tue, 29 Oct 1996 10:21:51 -0800 (PST) Received: from campa.panke.de (anonymous214.ppp.cs.tu-berlin.de [130.149.17.214]) by mail.cs.tu-berlin.de (8.6.13/8.6.12) with ESMTP id TAA26199; Tue, 29 Oct 1996 19:01:06 +0100 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id QAA03247; Tue, 29 Oct 1996 16:51:12 +0100 Date: Tue, 29 Oct 1996 16:51:12 +0100 From: Wolfram Schneider Message-Id: <199610291551.QAA03247@campa.panke.de> To: John Fieber Cc: ports@freebsd.org Subject: Re: www.freebsd.org/ports/index.html In-Reply-To: References: <199610282040.VAA00635@campa.panke.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Fieber writes: >However, just using the INDEX file will fail in detecting many >updates because only a few selected bits of the Makefile are >reflected the INDEX. With a checked out ports tree, I'll have to >dig through the CVS directories to discover the most recent date >change. Maybe the Makefile target that generates INDEX could do >this? Hmmm.... cvs -q rdiff -D'last week' -Dtoday ports | sed -n 's/^Index: //p' Print all files, which have been changed last week. Of course it is slow, ~20 min. Wolfram