If you use the standard emerge -u xawtv and X is running everything appears to install fine except that the LED fonts will not work. This is only noticable in full screen mode in XawTV. XFS needs to know the location of the LED fonts, /etc/X11/fs/config needs the following line added. /usr/X11R6/lib/X11/fonts/xawtv, to the catalogue and an /etc/init.d/xfs restart issued. NOTE!: X will get terribly slow if xfs is stopped for any reason, a restart will appear to lock up the system momentarily. I *really* like the font scanning done prior to XFS starting up, this was a MUCH needed feature, thanks.
I forgot to mention that this can be used to get rid of the xset command xawtv used. Just install the font and do a mkfontdir, modify the font servers config and restart XFS. This only works if XFS is used by default, I don't know what problems will occur if you use X without XFS.
ok, here's what I wanna know -- this font will not work with fontconfig? Because if it will, that will make things easier, I should think. Foser, thoughts?
uh the font will probably show up in fontconfig, but xawtv doesn't use xft2. So the 'old' X fonts setup stuff is still needed here. I don't think it's a good idea to get rid of the xset stuff, the problem is that there are more ways to provide fonts for X and every one of them uses other configuration files and for full support we should have every fonts ebuild (or one that provides fonts) update all relevant configs. That may not sound too complicated, but altering configfiles might prove to be difficult. Overwriting them might not be a good idea (ppl updating might forget to merge them right, losing other fontpaths etc.), diffs probably will fail. Maybe there's a better way by setting global fontpath environment vars. I'm not sure this is possible and haven't looked into it, but there must be a better way than poking in /etc all the time. In that respect xset isn't all bad (but not useful for xfs).
Should be fixed in CVS.... Please test.
