On Wed, Aug 29, 2012 at 5:42 PM, Michał Górny wrote:
> In other words, pkg-config is only used when no other criteria allows
> it to classify the particular .la file as suitable for removal or not.
> Sadly, it's rather, ehm, unfriendly to ebuild developers who obviously
> don't even read the relevant part.
>
> Do you have any ideas how we can improve that?
before the func executes pkg-config, run `has virtual/pkgconfig
${DEPEND}` and spit an eqawarn if it's not found
> One thing that comes into my mind is finally making pkgconfig
> a required, implicit part of toolchain (or @system). Since we have
> pkgconf now, this is more feasible than before.
i don't think making it part of the toolchain makes sense. i'd rather
not add it to @system simply to keep a few packages from sometimes
failing.
-mike
