From owner-freebsd-ports@FreeBSD.ORG Tue Sep 14 00:31:40 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 263DF16A4CE for ; Tue, 14 Sep 2004 00:31:40 +0000 (GMT) Received: from smtp806.mail.sc5.yahoo.com (smtp806.mail.sc5.yahoo.com [66.163.168.185]) by mx1.FreeBSD.org (Postfix) with SMTP id C1B4743D49 for ; Tue, 14 Sep 2004 00:31:39 +0000 (GMT) (envelope-from krinklyfig@spymac.com) Received: from unknown (HELO smogmonster.com) (jtinnin@pacbell.net@64.171.1.210 with login) by smtp806.mail.sc5.yahoo.com with SMTP; 14 Sep 2004 00:31:39 -0000 From: Joshua Tinnin To: freebsd-ports@freebsd.org Date: Mon, 13 Sep 2004 17:31:58 -0700 User-Agent: KMail/1.7 References: <20040913225637.GA12665@werd> In-Reply-To: <20040913225637.GA12665@werd> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409131731.59167.krinklyfig@spymac.com> cc: Jonathan Weiss cc: hsn@netmag.cz cc: Radek Kozlowski Subject: Re: Drop of portindex X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: krinklyfig@spymac.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2004 00:31:40 -0000 On Monday 13 September 2004 03:56 pm, Radek Kozlowski wrote: > On Mon, Sep 13, 2004 at 02:19:35PM -0700, Jonathan Weiss wrote: > > Cheers, > > > > > > I just noticed that portindex was removed from the ports-tree: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/71534 > > > > I just started to use portindex as an faster replacement for > > portsdb and I ask myself if there are any issues with further using > > it. > > > > Are there any problems with portindex or why it is dropped? > > Radim, can you please clarify under what licence you've released the > previous versions of portindex? > > I have to say that I'm very surprised by your decision, as portindex > is a great program and many people (myself included) started to like > it (and use it). Pity. Wow ... considering that a lot of people are using portindexdb as a workaround to the current ruby core dumping problem with portsdb, this deletion will have wide ranging consequences. I changed my ports database to fix it, but I still use portindex nearly every day. Is there any way to salvage this? (I'm not a programmer, or I'd offer to take it over ...). - jt