Re: pkg/32733: shared-mime-info buildlink pkg-config wrapper doesn't find all modules

[joerg%britannica.bec.de@localhost]

The following reply was made to PR pkg/32733; it has been noted by GNATS.

From: joerg%britannica.bec.de@localhost
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: pkg/32733: shared-mime-info buildlink pkg-config wrapper doesn't 
find all modules
Date: Sat, 4 Feb 2006 19:33:37 +0100

 On Sat, Feb 04, 2006 at 06:25:01PM +0000, Jussi Liukkonen wrote:
 >  >  Do you mean you want to use a native
 >  >  package instead of the pkgsrc one and it doesn't pick up the  
 >  > pkgconfig
 >  >  file of the native one?
 >  
 >  Exactly. The point of pkgconfig is to make things like this (using  
 >  modules installed in various places) easy by encapsulating the build  
 >  parameters behind a well-known abstraction. Not utilizing it sort of  
 >  defeats the purpose of the mechanism (as well as breaks pkgsrc's  
 >  PREFER_NATIVE/USE_BUILTIN mechanism).
 
 No, the point of pkg(-)config is to workaround the brain-damaged mess
 created in hundred tousand autoconf scripts. But that's a different
 issue.
 
 The real problem is that the builtin.mk support now has to deal with
 either copying or linking the native .pc files if available. This is
 further complicated by its possible omission on some platforms. Just
 pushing /usr/lib/pkgconfig or wherever they are for native pkgconfig is
 *not* an option, since that would remove all the protection against
 overaggressive configure scripts buildlink3 offers.
 
 Joerg