Date: Thu, 28 Sep 2006 07:57:12 -0700 From: "Bill Blue" <bblue@netoldies.com> To: "Doug Barton" <dougb@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: x11/xmixer, multimedia/ruby18-shout, etal Followup Message-ID: <op.tglftmdlzq5pz4@sovaio.netoldies.com> In-Reply-To: <451ACE49.7000300@FreeBSD.org> References: <op.tf65j3kzzq5pz4@sovaio.netoldies.com> <op.tf675bmgzq5pz4@sovaio.netoldies.com> <451ACE49.7000300@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 27 Sep 2006 12:17:29 -0700, Doug Barton <dougb@FreeBSD.org> wrote: > 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. Thanks Doug, for portmaster and your support. --Bill
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.tglftmdlzq5pz4>