Bug 165781

Description Alberto Villa 2012-03-06 17:20:13 UTC

Font ports are currently handled by hand, one by one, while most of the tasks (like updating font cache) could be automated. X.Org font ports have a draft of such a system, but a bit bugged, and not suited for non-X.Org ports (some try to use it, with some hacks). Additionally, all the @(un)?exec's used in those ports fail with pkgng, thus being an obstacle to its growth.

Fix: The attached patch proposes an evolution of the system already there for X.Org ports, which takes care of most of the procedures required by font ports:
- setting installation directory (different for X.Org and non-X.Org ports) without hardcoding it (thus making it flexible);
- creating and removing installation directories;
- updating font cache;
- printing a default pkg-message to notify users about the need to update xorg.conf(5).
It has been reviewed and approved by x11@ (via kwm@), apart for documentation which still requires work.

It fully supports pkgng, and introduces extension scripts for plist. Keywords/fontdir.yaml provides a @fontdir plist directive which updates font cache for a directory and removes the directory on deinstallation.
This has been approved by portmgr@ (via bapt@).

The system can be included with XORG_CAT=font for X.Org ports, and INSTALLS_FONTS=yes otherwise.

I'm now asking for an exp-run to check for errors.

Please note: the attached patch contains bits which have to go in at the same time. Without them all, fail is ensured. Here - http://people.freebsd.org/~avilla/files/fonts/fonts-full.diff - you can find a patch containing the fixes for *all* (120) font ports. As I expect it will take some time to get approval for all of them (at most two weeks, for maintainer timeout), I'd like to start committing the smaller patch, and then update single ports when maintainers reply.

Patch attached with submission follows: