From owner-freebsd-chat Thu Feb 18 9:20:45 1999 Delivered-To: freebsd-chat@freebsd.org Received: from toxic.magnesium.net (toxic.magnesium.net [204.188.6.238]) by hub.freebsd.org (Postfix) with SMTP id 3DEAA116FC for ; Thu, 18 Feb 1999 09:20:38 -0800 (PST) (envelope-from unfurl@toxic.magnesium.net) Received: (qmail 41821 invoked by uid 1001); 18 Feb 1999 17:20:36 -0000 Date: 18 Feb 1999 09:20:36 -0800 Date: Thu, 18 Feb 1999 09:20:36 -0800 From: Unfurl To: chat@freebsd.org Subject: Re: Port upgrade check/report tool Message-ID: <19990218092036.A41753@dub.net> References: <199902181150.WAA13777@whirlwind.netspace.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902181150.WAA13777@whirlwind.netspace.net.au>; from gcross@netspace.net.au on Thu, Feb 18, 1999 at 10:47:04PM +1100 Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Feb 18, 1999 at 10:47:04PM +1100, gcross@netspace.net.au wrote: > I haven't found a tool that will look at the current ports index file, > then look at the ports installed on my system and tell me which ports > are now out-of-date and need upgrading. > > So, I have written a Python program that will do just that. > > It will work with either a local copy of a current ports INDEX file, or > fetch one (via ftp or http) from a FreeBSD site. > > Out of sheer originality, I have named it portcheck, and you can read > about it and download the tarball from: > > http://www.netspace.net.au/~gcross/portcheck.html > > I would appreciate comments, bug reports, etc, before I announce it to > a wider audience. Why not just use cvsup? -Bill -- unfurl@dub.net - This is a munition. Fight Back! #!/bin/perl -sp0777i