new fontconfig is out. Please version bump the unstable version. This release has been optimized for speed, so there should be a noticable difference to previous versions. Thanks
It's a development release, ~arch is not meant for that. Someone should look into if and how the cache changes affect the font eclass functioning.
Fontconfig 2.3.95 is out now since a couple of weeks. It's stable enough for everyday use and other distros (fedora, suse) are already shiping with it. I agree that it should be imported. It could be hardmasked if you don't think it's ready for ~arch.
(In reply to comment #2) > Fontconfig 2.3.95 is out now since a couple of weeks. It's stable enough for > everyday use and other distros (fedora, suse) are already shiping with it. I > agree that it should be imported. It could be hardmasked if you don't think > it's ready for ~arch. > Fontconfig 2.3.95 is a 2.4.0 release candidate. and the site says: The current stable series is 2.3. The latest version in that series is 2.3.2 So, IMHO, it shouldn't be imported.
People, fontconfig 2.4.0 was released two days ago. I think it should get into portage tree ASAP, cause it's the only real blocker for freetype 2.2 .
BTW, as cache handling has changed, font.eclass needs to be changed too, otherwise ACCESS VIOLATION will occur. I don't now if following change is 100% correct, but it works for me. font_xft_config() { addwrite /var/lib/cache/fontconfig # create fontconfig cache einfo "Creating fontconfig cache ..." # Mac OS X has fc-cache at /usr/X11R6/bin HOME="/root" fc-cache -f -s "${D}${FONTDIR} } -s stands for --system-only
fontconfig-2.4.1 has been added the eclass has been updated as needed.
