x11/xmixer, multimedia/ruby18-shout, etal Followup

Bill Blue bblue at netoldies.com
Thu Sep 28 07:57:01 PDT 2006

On Wed, 27 Sep 2006 12:17:29 -0700, Doug Barton <dougb at 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.


More information about the freebsd-ports mailing list