On 23 Apr 2003, Jeremy Portzer wrote: > On Wed, 2003-04-23 at 01:41, Rodolfo J. Paiz wrote: > > At 02:02 PM 4/22/2003 -0400, you wrote: > > >On Tue, 2003-04-22 at 12:09, Christopher Wong wrote: > > > > Why am I even bothering with this? Hint: Red Hat's freetype is > > > > crippled. TrueType fonts look much better -- with or without > > > > antialiasing -- when bytecode interpretation is turned on. I know > > > > the usual explanation: patent question, CYA, yadda, yadda. > > > > > >You're making life difficult on yourself. Just download the freetype > > >SRPM, install it with rpm -i, and turn on the bytecode interpreter > > >with a simple change to the spec file. Thanks for the suggestion. To answer my own question, Red Hat packages multiple versions of freetype in their RPM: freetype 1.4 and 2.1.3. While playing with this stuff, I hit some unexpected behavior. Initially I renamed the original Red Hat libfreetype.so.6.3.2 and installed my own version with bytecode interpretation enabled: /usr/lib/libfreetype.so.6.3.2 /usr/lib/libfreetype.so.6 -> libfreetype.so.6.3.2 /usr/lib/libfreetype.so.6.3.2.old (the original file) (etc) But once in a while the symlink gets changed spontaneously to point to the old lib: /usr/lib/libfreetype.so.6.3.2 /usr/lib/libfreetype.so.6 -> libfreetype.so.6.3.2.old /usr/lib/libfreetype.so.6.3.2.old (the original file) Does anyone know what is responsible for this behavior? Gremlins? Thanks. Chris
