From owner-freebsd-ports@FreeBSD.ORG Fri Oct 22 22:30:24 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A811216A4D4 for ; Fri, 22 Oct 2004 22:30:24 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D36043D39 for ; Fri, 22 Oct 2004 22:30:11 +0000 (GMT) (envelope-from freebsd-ports@m.gmane.org) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CL7vG-0002Kj-00 for ; Sat, 23 Oct 2004 00:30:10 +0200 Received: from pcp08490587pcs.levtwn01.pa.comcast.net ([68.83.169.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 23 Oct 2004 00:30:10 +0200 Received: from apeiron by pcp08490587pcs.levtwn01.pa.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 23 Oct 2004 00:30:10 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: Christopher Nehren Date: Fri, 22 Oct 2004 18:18:41 -0400 Lines: 32 Message-ID: References: <20041022153854.GA88362@happy-idiot-talk.infracaninophile.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: pcp08490587pcs.levtwn01.pa.comcast.net User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) Sender: news Subject: Re: portindex -- the second coming. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2004 22:30:24 -0000 On Fri, 22 Oct 2004 17:38:54 +0100, Matthew Seaman wrote: > Dear all, > > After the recent fun and games with the sysutils/portindex port by > Radim Kolar, it seems there is a pent up demand for software that can > maintain /usr/ports/INDEX without the hassle of going through a full > 'make index' every time you want to update. > > I've put together a few bits of perl to achieve that. Now I'm looking > for people to try it out, send me feedback, bug reports, suggestions > etc. To be beta testers in fact. Yum. I also appreciate your choice of implementation language. :) Although, actually, the main reason for why I liked portindex was that it made an extremely detailed entry of every single port in a PostgreSQL database. You could then make complex queries against that database using SQL. You could see which ports you had installed which depended upon a group of ports that matched a regex, for example (using subqueries -- which is one of the reasons why I'm glad that PostgreSQL was chosen, instead of a certain overly popular RDBMS which shall remain nameless which lacks this feature). I don't know about others, but the SQL interface is much more intuitive for me than using make syntax. And it's more flexible, too. Not to mention that you can easily make graphs from it, and so forth ... If you're interested, I'd like to implement the RDBMS side of your portindex replacement. I'll take a look at your replacement later tonight, and shall give further feedback either then or tomorrow.