I'm going to package xawtv (http://linux.bytesex.org/xawtv) for Fedora. This package was in Fedora Core until FC2 (then switch to tvtime). Since there are a couple of useful utils (cmdline, radio, alevtd web teletext etc.), "xawtv" still seems to be useful enough. Traditionally, "xawtv" includes a "tv-fonts" package, which correlates with "zvbi-fonts". tv-fonts includes 3 parts: - "led fixed" fonts for fullscreen mode. Can be omitted now (f.e. truetype "bitstream vera" looks fine for the same purpose). - "ets caption" seems to be the same as in zvbi-fonts - "ets teletext", containing 3 size, whereas "zvbi-fonts" contains only one. Since "led fixed" IMO can be dropped now, hypothetical "tv-fonts" and "zvbi-fonts" will look identical. Hence it could be useful to use one common package. First, I hope to get rid of tv-fonts at all, but to see teletexts properly on my browser, I have to return "20pxl" font back ("teletext2.pcf"). OTOH, zvbi upstream creates only one "10pxl" font... :( What is your thoughts about this? Whether the common package is good, and what package to take as a base for it?
Well it appears that the xawtv package offers more fonts. Zvbi actually doesn't depend on those fonts, they are encoded internally in the program, but it also compiles standalone versions for use by other programs. So one suggestion would be for me to update the zvbi package so that it doesn't produce a zvbi-fonts package. You package the fonts from xawtv as something like xawtv-fonts or tv- fonts. This should also obsolete zvbi-fonts so that there's a smooth upgrade. What do you think?
> You package the fonts from xawtv Actually, "xawtv-tv-fonts" is not xawtv-related. This (sub-)package has another source tarball: "tv-fonts-1.1.tar.gz". "tv-fonts" uses the same way to create the fonts as "zvbi" does: it compiles and run "x11font" binary, which includes "exp-gfx.c" source directly when compiled. Since "xawtv" has not zvbi code, it provides some (certainly obsoleted) copy of exp-gfx.c, whereas "zvbi" package always uses the lates one. Hence this fonts actually are "zvbi'-ralated. The difference between "tv-fonts" and "zvbi-fonts" is that "tv-fonts" has a little different x11font.c source, which is capable to produce 3 type of fonts instead of one. Therefore I think we should just patch zvbi's "contrib/x11font.c" file and then generate 6, not 2, fonts in .spec file. If you agree whith this, I'll provide all needed patches.
Sure, I have no problem with this. If you send the patches, I'll update the package.
Created attachment 149824 [details] patch for contrib/x11font.c, add missed features from tv-fonts package ...
Created attachment 149825 [details] A needed changes for .spec file Besides the patch above, I suggest some more changes: - move 'bdftopcf' compiling and friends to build stage (not install) - support for old xfs font system (mkfontdir, chkfontpath etc.) - add correspond Requires(post,postun) for zvbi-fonts package - zvbi-fonts now obsoletes xawtv-tv-fonts Feel free to write some changelog entry for this, and update to the latest upstream (0.2.24 ? ;) )
Thanks for that. I've implemented most of the suggestions. The spec file, source RPM and changelog can be found below. Unless there's anything majorly wrong (hopefully not, but it's late and I'm tired :-D ) with it, I'll push this update soon. http://dribble.org.uk/reviews/zvbi.spec http://dribble.org.uk/reviews/zvbi-0.2.24-1.src.rpm * Tue Mar 13 2007 Ian Chapman <packages> 0.2.24-1%{?dist} - Upgrade to 0.2.24 - Convert README and ChangeLog to UTF-8 - Added patch for x11font to generate more font sizes useful for other applications such as xawtv (courtesy of Dmitry Butskoy) - Fonts sub-rpm now obsoletes and provides xawtv-tv-fonts - Split font generation and font installation into separate sections - Various other minor changes to the spec - Added xfs support for the fonts
Looks fine! Thanks! Ian, please, update FC-5 and FC-6 too (not devel only :) )
No problem. I always push for all releases where possible. :-)
Built successfully and pushed to the repo. Closing.