From owner-freebsd-hackers Thu Sep 30 14:14:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from r84aap011262.sbo-smr.ma.cable.rcn.com (r84aap011262.sbo-smr.ma.cable.rcn.com [209.6.194.47]) by hub.freebsd.org (Postfix) with ESMTP id CC3C314E62 for ; Thu, 30 Sep 1999 14:14:14 -0700 (PDT) (envelope-from huff@r84aap011262.sbo-smr.ma.cable.rcn.com) Received: (from huff@localhost) by r84aap011262.sbo-smr.ma.cable.rcn.com (8.9.3/8.9.3) id RAA11471; Thu, 30 Sep 1999 17:14:14 -0400 (EDT) (envelope-from huff) From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14323.53925.815819.699822@r84aap011262.sbo-smr.ma.cable.rcn.com> Date: Thu, 30 Sep 1999 17:14:13 -0400 (EDT) To: freebsd-hackers@FreeBSD.org Subject: RE: updating packages automatically, etc.pp. In-Reply-To: <101308237@toto.iv> X-Mailer: VM 6.72 under 21.1 "20 Minutes to Nikko" XEmacs Lucid (patch 2) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway writes: > > The script relies on you having an up-to-date INDEX file; do "make > > index" first to be sure (which reminds me, why is the INDEX file > > always out of sync after a cvsup?). It only tries to upgrade ports > > Because it's only generated periodically, not every time someone > adds or modifies a port, which would be very wasteful. How often is periodically? While I read the output of my CVSup sessions, it had been my impression that INDEX was an accurate (+/- epsilon) snapshot of the ports tree. Are you telling me it could be, oh, two or three weeks out of date ...? Robert Huff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message