omz13

Freetype 2.2.1 has been announced, and I’ve added to my set of ebuilds one to grab this release from the freetype CVS repository.

To get my ebuilds for freetype into your local portage tree, simply do:

# rsync -rztv --delete rsync://rsync.omz13.com/local-portage/media-libs/freetype /usr/local/portage/media-libs

Then emerge =freetype-cvs.2.2.1 to get 2.2.1 direct from the freetype CVS repository.

(c.f. gentoo bug #123683)

freetype-2.2.0 was tagged late last night in the freetype CVS repository ready for its impending release (although don’t be surprised if the tag gets moved before 2.2 is really released).

For those unable to wait for the official 2.2 release and tarballs, you can use my nifty ebuild that grabs the tagged source from the CVS repository. Its working back here and looks great (no more rendering issues for me). Of course, there are some issues with going to freetype-2.2.0, but IMHO it really is a worthwhile upgrade.

To get my ebuilds for freetype into your local portage tree, simply do:

# rsync -rztv --delete rsync://rsync.omz13.com/local-portage/media-libs/freetype /usr/local/portage/media-libs

Then emerge =freetype-cvs.2.2.0 to get 2.2.0 direct from the freetype CVS repository.

After installing freetype-2.2.0-RC4 (using my handy freetype-cvs.2.2.0_rc4.ebuild) it appears that it breaks xorg-x11-6.8.2-r6 on my gentoo-based system.

(more…)

After installing RC4 of freetype-2.2.0 from cvs (gentoo people can use my ebuild), it would appear that this release candidate still has a few rendering problems, as shown in the accompanying image.
 

Freetype-2.2.0-RC4 has been tagged in the freetype cvs repository, so I have now made an ebuild to pick up this (bleeding-edge) release.

(more…)

I’ve created two ebuilds that install the HEAD and 2.2.0-RC3 of freetype from its cvs repository. This is rather handy for people who want to be on the bleeding edge of freetype development/usage.

(more…)