Re: pkgsrc picking up wrong fontconfig

[Thomas Klausner <tk%giga.or.at@localhost>]

On Fri, Aug 30, 2019 at 08:08:08PM -0400, Greg Troxel wrote:
> But if foo-2 depends on bar-2 (but foo-1 depends on only bar-1), and you
> have foo-2 installed, then if baz depending on foo is built, it is a bug
> if it links against bar-1.  That is what is happening.
> 
> I see your point about old packages, but I think we need to prioritize
> correctness over optimizing dependencies for non-current installs.
> 
> > If you say we need to depend on the latest pango (i.e. bump ABI
> > depends in bl3.mk), then we could add its BUILDLINK_API_DEPENDS
> > pattern for fontconfig to its bl3.mk file.
> 
> When foo depends on bar, and foo's bl3 has bar, then anything that
> depends on foo (via bl3) has to end up with the *same bar* that foo
> used.  Lacking a mechanism to do exactly that, we have to have a safe
> approximation.[q
> 
> Really the whole notion of native vs pkgsrc X libs, other than a great
> native/modular divide, is not really sound.  If native isn't fully ok,
> so that we can build everything with only native, we have to either give
> up on native entirely or give up on the modules that are semi-ok.

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.

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.
 Thomas