Re: pkgsrc picking up wrong fontconfig

[Greg Troxel <gdt%lexort.com@localhost>]

Thomas Klausner <tk%giga.or.at@localhost> writes:

> On Sat, Aug 31, 2019 at 07:23:22AM -0400, Greg Troxel wrote:
>> Thomas Klausner <tk%giga.or.at@localhost> writes:
>> 
>> > The longer I think about this, the more it reminds me of the gcc
>> > issue. Basically it should be a global setting, but it's decided on a
>> > per-package level.
>> 
>> Yes, that's what I was trying to say...
>
> Sorry for being slow :)

I meant: you said it much more concisely.

>> > For pango, the workaround seems easier than for gcc - we can just make
>> > everyone depend on the latest pango (and latest fontconfig). Add the
>> > fontconfig + freetype2 version patterns from the Makefile to the
>> > buildlink3.mk file and bump the API (I think, since we don't want it
>> > to be overridable) depends, then bump all users.
>> 
>> I don't think pango is the problem; it's just fontconfig.   And pango
>> requiring new fontconfig  means every other program that uses fontconfig
>> that could possibly also be linked with pango (or something that could be
>> linked with something that could be linked with pango, transitive
>> closure) has to use the new fontconfig.
>> 
>> So what I want to do is set the BUILDLINK_API_DEPENDS in fontconfig/bl3
>> to 2.11.91.  That means native fontconfig on -8 will never be used by
>> pkgsrc, I think.
>> 
>> (There may be a similar freetype2 issue.)
>
> Yes, I think that's probably the best solution.
> Will need a recursive bump though.

OK - I have been doing a pkg_rr with the change in place, and will commit it
later today.