From owner-freebsd-ports@FreeBSD.ORG  Fri Jan 30 14:07:58 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 89CB116A4CE
	for <ports@freebsd.org>; Fri, 30 Jan 2004 14:07:58 -0800 (PST)
Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0ADFB43D41
	for <ports@freebsd.org>; Fri, 30 Jan 2004 14:07:51 -0800 (PST)
	(envelope-from linimon@lonesome.com)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id A726A146F8; Fri, 30 Jan 2004 16:07:50 -0600 (CST)
Date: Fri, 30 Jan 2004 16:07:50 -0600 (CST)
From: Mark Linimon <linimon@lonesome.com>
X-X-Sender: linimon@pancho
To: Trevor Johnson <trevor@jpj.net>
In-Reply-To: <20040130162952.B93054@blues.jpj.net>
Message-ID: <Pine.LNX.4.44.0401301603590.13953-100000@pancho>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: ports@freebsd.org
cc: Kris Kennaway <kris@obsecurity.org>
Subject: Re: big PLIST_FILES patch
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2004 22:07:58 -0000

On Fri, 30 Jan 2004, Trevor Johnson wrote:
> kris wrote:
> > When do you think you'll be able to fix all those plist problems in
> > your ports, and other port build failures?  I'd prefer you did this
> > before working on other port changes, since they've been broken for
> > going on 3 months or more now.
> 
> I don't know of any with wrong packing lists. I think some of my ports
> were broken by the renaming of rpm2cpio to rpm2cpio.pl seven weeks ago,
> which is what you're probably referring to.  I'll check into those soon.

At the moment I'm still working on moving my code over to this
new box, and thus there are still some errors, but my ports
monitoring code is great at being able to cross-reference
build errors, PRs, and so forth.

The URL to look at a report of all PRs and build errors for a single
maintainer is at, e.g.,
http://portsmon.firepipe.net/portsconcordanceformaintainer.py?maintainer=trevor@FreeBSD.org

mcl