From owner-freebsd-ports@FreeBSD.ORG  Mon Jun 19 07:37:53 2006
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: 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 798EA16A479
	for <ports@freebsd.org>; Mon, 19 Jun 2006 07:37:53 +0000 (UTC)
	(envelope-from sem@FreeBSD.org)
Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 13AEF43D46
	for <ports@freebsd.org>; Mon, 19 Jun 2006 07:37:53 +0000 (GMT)
	(envelope-from sem@FreeBSD.org)
Received: from msd.mbrd.ru ([172.16.33.193])
	by relay-er5.mbrd.ru with esmtpa (Exim 4.x)
	id 1FsEKV-000NUP-RC; Mon, 19 Jun 2006 11:37:51 +0400
Message-ID: <4496544F.7060006@FreeBSD.org>
Date: Mon, 19 Jun 2006 11:37:51 +0400
From: Sergey Matveychuk <sem@FreeBSD.org>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: noackjr@alumni.rice.edu
References: <44962FED.7050109@alumni.rice.edu>
In-Reply-To: <44962FED.7050109@alumni.rice.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ports@freebsd.org
Subject: Re: portsclean deleting too many distfiles
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
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: Mon, 19 Jun 2006 07:37:53 -0000

Jonathan Noack wrote:
> I did not specify it twice (because I have 'portsclean -D' aliased to
> 'pc') so I guess there is a regression in portupgrade 2.1.4.

The bug is in option parser. It works some way before, but after I did
more smooth initializer it has risen. I've committed a work around and
will recheck all other options.

-- 
Dixi.
Sem.