BaSS tested this one and it broke with pango could you check this one with the debian FreeType 2.1.2 package if you have time? they had some patches in there..
The debian patch for 2.1.2 doesn't include any pango related fixes. have you recompiled pango since the installation of the new freetype? Maybe any other programs that depended on freetype for that matter?
I think that bass@gentoo.org is the one for this :)
bass! What are you seeing wrong with pango? I haven't had any problems with the build as of yet.
okay, I've ran it through some testing and it works for me... I want more arch tests and more systems, got one positive off list mail that it works.
Created attachment 2788 [details] Fix to enable font hinting as was done in previous versions Font hinting hasn't been enabled, so it will break things if you upgrade from previous versions. However, it is easy to re-enable, just add the attached fix to the ebuild. Note: ....#undef TT_CONFIG_OPTION_BYTECODE_INTERPRETER.... ^^ The 2 spaces in the first part of the statement are necessary because they changed the souces to this format. Otherwise, sed will not process the change!
I added your fix onto the freetype-2.1.2 ebuild. Please test and let me know if you have success with this fixed ebuild.
Created attachment 2824 [details] metacity error with freetype-2.1.2 freetype-2.1.2 builds and runs great, but dependencies broken. Here metacity
Freetype builds fine here (I patched BYTE_CODE blahblah manually) But dependencies, like metacity, are broken now.
Re-emerge pango and then emerge metacity. The compile problem seems to be due to the fact that pango is not aware of the new freetype capabilities. Let me know if things end up working for you.
I re-emerged pango after emerging freetype-2.1.2 and the dependencies are fine now. Metacity built successfully!
I just wanted to report back that it is now enabling font hinting. Thanks for taking this into considieration!
Are there any more open issues with freetype-2.1.2 or does it seem safe to unmask? If there are no objections I will unmask it and mark this bug FIXED in a day or two.
Could you hold off until just before we upgrade and unmask the new batch of Gnome libs that include the new pango? To unmask it at the same time would reduce the problems with users not rebuilding pango after installing freetype 2.1.2
I'm marking the bug as fixed so that users realize the ebuild is ready for consumption. When you unmask other said gnome applications and libraries, go ahead and unmask freetype-2.1.2 from package.mask.
