SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Latest update on the infinality website is for freetype-2.4.12, but slackware64 14.1 has freetype-220.127.116.11. What patches did you apply? This shows how to patch freetype but the patch is for 2.4.12 and not 2.5.0.
Click here to see the post LQ members have rated as the most helpful post in this thread.
I removed the last section that patches these files
There were some substitution problems with some sites on firefox that used sans-serif as the font. The rendering was clear and nice. But I think the somewhat wider spacing also caused problems with some guis.
Anyway, I also followed dugan's nice advices and I have settled for this minimal updated freetype-2.5.2 along with the default slackware64-14.1 fontconfig that I use now. You have to enable the patch lines yourself to enable the patches in the slackbuild. It contains the cleartype.diff patch posted above. I also used dugan's fonst.conf.
EDIT: Use this slackbuild only for testing, it seems to break compiling other packages that include freetype, the headers are not installed correctly.
Ready build packages (the freetype package is for x86_64 only, use the slackbuilds below for 32 bit)
EDIT: Since I don't know if it allowed to share this compiled
due to licensing, use the slackbuilds below to build freetytpe.
If it's ok, I can share the prebuild package again. fontconfig-infinality-1-20130104_1-noarch-1did.txz
Download the two above packages and then
Reboot and enjoy infinality
The updated infinality patch freetype-entire-infinality-patchset-20131213-01.patch
(ttinterp.c) Removed all patches except one, all the rest seem to included upstream
(ttsubpix.c) Removed patches since the changes are included upstream
(ttsubpix.h) Removed patches since the changes are included upstream
Thanks, I installed according to the guide.
Now slackpkg shows that I have an update to freetype, namely freetype-2.5.0-1-x86_64-1.txz
Should I skip this update? Becuase it would update the freetype package made with infinality..
So should I add freetype to /etc/slackpkg/blacklist?
Or in other words how to maintain this package w.r.t official freetype?
Thanks, I put freetype* in /etc/slackpkg/blacklist.
Now if there was an update to freetype, would slackpkg show it or not..(and how would I know if there was an update or not without checking manually myself if slackpkg didnt show it)..
Perhaps I would have to rebuild the freetype package with the updated source if a new version came out..