On Monday 17 of November 2014 09:27:07 İsmail Dönmez wrote:
On 16 Nov 21:22, šumski wrote:
On Sunday 16 of November 2014 20:54:39 İsmail Dönmez wrote:
On 14 Nov 23:28, Achim Gratz wrote:
İsmail Dönmez writes:
Yes, but this shouldn't result in any functionality change. Let me know if otherwise.
This is what zypper tells me will happen:
--8<---------------cut here---------------start------------->8---
The following 11 packages are going to be downgraded: cairo-devel 1.14.0-98.1 -> 1.12.16-8.1 libcairo-gobject2 1.14.0-98.1 -> 1.12.16-8.1 libcairo-script-interpreter2 1.14.0-98.1 -> 1.12.16-8.1 libcairo2 1.14.0-98.1 -> 1.12.16-8.1 libqt4 4.8.6-371.1 -> 4.8.6-8.1 libqt4-devel 4.8.6-371.1 -> 4.8.6-8.1 libqt4-linguist 4.8.6-371.1 -> 4.8.6-8.1 libqt4-qt3support 4.8.6-371.1 -> 4.8.6-8.1 libqt4-sql 4.8.6-371.1 -> 4.8.6-8.1 libqt4-sql-sqlite 4.8.6-371.1 -> 4.8.6-8.1 libqt4-x11 4.8.6-371.1 -> 4.8.6-8.1
--8<---------------cut here---------------end--------------->8---
If you think that's OK, I'll go ahead with the update over the weekend. The version bump for cairo was relatively recent, so I don't think anything depends on it yet.
ACK this is safe. And the reason for this change is we only need modified freetype2 package now. Rest will dynamically load the needed functionality.
AFAIK, Qt still renders fonts differently depending whether FT_CONFIG_OPTION_SUBPIXEL_RENDERING was defined. IOW, Qt built against 'plain' freetype2 and 'patched' freetype2 will not render fonts in the same manner...
If I am not mistaken https://build.opensuse.org/package/view_file/KDE:Qt/libqt4/use-freetype-def ault.diff?expand=1 checks for subpixel availability on runtime.
I don't have the Qt4 sources locally (so can't check when is that invoked), but QFontEngineFT::loadGlyph depends on FT_CONFIG_OPTION_SUBPIXEL_RENDERING during compile time. Maybe it is unused these days... Cheers, Hrvoje
Regards, ismail