From owner-freebsd-ports@FreeBSD.ORG Wed Sep 27 19:17:35 2006 Return-Path: X-Original-To: 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 84F1116A416 for ; Wed, 27 Sep 2006 19:17:35 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.FreeBSD.org (Postfix) with SMTP id EC44A43D45 for ; Wed, 27 Sep 2006 19:17:34 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 14603 invoked by uid 399); 27 Sep 2006 19:17:33 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 27 Sep 2006 19:17:33 -0000 Message-ID: <451ACE49.7000300@FreeBSD.org> Date: Wed, 27 Sep 2006 12:17:29 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.7 (X11/20060917) MIME-Version: 1.0 To: Bill Blue References: In-Reply-To: X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: x11/xmixer, multimedia/ruby18-shout, etal Followup X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 19:17:35 -0000 Bill Blue wrote: > Ok, I have found the problem. I had mis-specified the port group > that a particular port was in. xmixer is in audio, not x11, for > example. > > if you use portmaster's -p option to specify the path to a port and > that path doesn't exist, portmaster will display a message that the > path is not found and no xref is found, but then proceed to clean > for ' ', which essentially walks through the entire tree. It > doesn't stop when the specified port is not found! The not found > messages go by quickly and I never saw them. Thanks for the reminder about this one, I keep thinking that I've fixed it, but obviously I hadn't. It is now fixed (hopefully for good!) in the latest version that I just announced. Doug -- This .signature sanitized for your protection