Freetype 2.1.7 and up default to a new include scheme that requires fixing older ebuilds that have not yet adapted to this format. Add bugs that are caused by this as blockers to this bug.
Created attachment 32381 [details, diff] new freetype patch for media-gfx/bootsplash-0.6.1 not sure whether this patch should be submitted here, if not, my appologies. attached a patch to the media-gfx/bootsplash-0.6.1 ebuild to make it work with freetype-2.1.7 this patch also works media-gfx/bootsplash-0.6-r16 and assume all bootsplash-0.6 ebuilds. hth
not here, create a seperate bug and make it block on this one.
Would be nice to get 2.1.9 out of p.mask by the time of the next xorg release, since that's what they plan to ship (they're at 2.1.8 now) and things may start breaking if our external version is much older. It's scheduled for August 25.
https://freedesktop.org/bugzilla/show_bug.cgi?id=925 is relevant to my previous comment.
Also http://freedesktop.org/pipermail/xorg/2004-July/001956.html. 2.1.8 is required by next xorg release, unless we build freetype statically within xorg build (which sucks) or patch in the new public API stuff.
bug #59849 mozilla (firefox) should block this too.
it's not a header type problem, what this bug was initially about. But i guess it wouldn't hurt to track it.
where are we waiting for? I suppose the affected ebuilds could have a simple check for which freetype is installed and a patch.
I suppose this bug can be closed...
you are correct sir, thank you.
