From owner-freebsd-ports Thu Nov 30 15:31:36 1995 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA04028 for ports-outgoing; Thu, 30 Nov 1995 15:31:36 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA04020 for ; Thu, 30 Nov 1995 15:31:31 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id PAA01103; Thu, 30 Nov 1995 15:24:09 -0800 To: Chris Stenton cc: asami@cs.berkeley.edu, ports@freebsd.org Subject: Re: new version of "updated" perl script. In-reply-to: Your message of "Thu, 30 Nov 1995 21:37:44 GMT." Date: Thu, 30 Nov 1995 15:24:09 -0800 Message-ID: <1101.817773849@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-ports@freebsd.org Precedence: bulk > OK, this version is for the people that don't keep their packages clean. > > Just running "updated" should give the user a nice clean list of packages > that s/he has installed but have since been updated. Actually, I was thinking a little about this just the other day.. :-) What say you folks about the idea of a "ports" command? It would probably be a perl script from hell, but it would basically do all the sorts of cutsie ports related things combined in one utility. For example, you could do things like: ports -cat all -grep name:emacs ports -cat editors -grep maint:jkh ports -cat all -show "name:\t${name}\ncategories:\t${cats}" And so on to get information on new ports, extract patch files for easy mailing, collect ports statistics, etc. ``ports -help'' would also display useful information about ports, how to create them, etc. As we think up new functionality, we simply add it to the single ports command so that it's easy to find. The current `index' targets in /usr/ports/Makefile hardly seems to do the ports collection justice! :-( Jordan