ports/98415: Port name problem

Tim Daneliuk tundra at tundaware.com
Sat Jun 3 05:00:35 UTC 2006


>Number:         98415
>Category:       ports
>Synopsis:       Port name problem
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jun 03 05:00:28 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Tim Daneliuk
>Release:        4.11-Stable
>Organization:
TundraWare Inc.
>Environment:
FreeBSD eskimo.tundraware.com 4.11-STABLE FreeBSD 4.11-STABLE #29: Fri Jun  2 16:33:32 CDT 2006     toor at eskimo.tundraware.com:/usr/obj/usr1/src/sys/ESKIMO  i386
>Description:
Many packages depend on the presence of the 'pkgconfig' tools.  However, for 
some reason, the port has recently been renamed to 'pkg-config'.  This is
causing all manner of aggravation because pre-compiled packages expect the
former to be installed and don't know that the latter is the same thing.
This means you have to go into the *ports* to build everything you want by
hand - ports (like pango, cairo, etc.) properly look for the dependent binaries
and libraries not the installed package name.

What gives? 
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list