From owner-freebsd-stable  Mon Mar 22 20:45:16 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from tick.ssec.wisc.edu (tick.ssec.wisc.edu [144.92.108.121])
	by hub.freebsd.org (Postfix) with ESMTP id B063E14D31
	for <stable@freebsd.org>; Mon, 22 Mar 1999 20:45:13 -0800 (PST)
	(envelope-from dglo@tick.ssec.wisc.edu)
Received: from tick.ssec.wisc.edu (localhost [127.0.0.1])
	by tick.ssec.wisc.edu (8.8.7/8.8.7) with ESMTP id WAA17794;
	Mon, 22 Mar 1999 22:44:44 -0600 (CST)
From: Dave Glowacki <dglo@SSEC.WISC.EDU>
Message-Id: <199903230444.WAA17794@tick.ssec.wisc.edu>
To: John Baldwin <jobaldwi@vt.edu>
Cc: Mike Meyer <mwm@phone.net>, stable@freebsd.org
Subject: Re: Musings about tracking FreeBSD... 
In-reply-to: Your message of "Mon, 22 Mar 1999 21:01:23 EST."
             <XFMail.990322210123.jobaldwi@vt.edu> 
Date: Mon, 22 Mar 1999 22:44:38 -0600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I have a very simple shell script that greps /usr/ports/INDEX to find ports
> that need updating.  It does have the rare false alarm (namely pgp-2.6.2). 

Bruce Mah's Perl script in /usr/ports/sysutils/pkg_version does this, too.

> Also, I find that /usr/ports/INDEX isn't always up to date with the rest of the
> ports tree, occasionally producing another false alarm, but these are easy to
> find by just checking the version in the respective ports Makefile.

You can also fix the out-of-date /usr/ports/INDEX problem by doing a
"make index" in /usr/ports, but this gives your disk a MAJOR workout
and takes a while to complete, so the fix might be worse than the problem.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message