On Tue, 2009-02-17 at 14:39 -0800, Russ Allbery wrote: > Could you comment on this from the Debian font team perspective? What's > the right thing to do in a case like this? I can comment from my perspective (best suggestion at the top): Firstly figure out what the font is doing in the package. If you can substitute any other font at all then just drop it and pick a smaller font package to depend on. If you can, use libfontconfig to find the font you prefer but fall back on whatever installed font is available. This way the dependency can be a recommends or a dep on one of several different fonts. Also, libfontconfig itself depends on ttf-dejavu | ttf-bitstream-vera | ttf-freefont | gsfonts-x11 so you are guaranteed to always have a font available when using fontconfig in Debian (Probably similar in Fedora and other distros). Getting this change upstreamed is a good idea too IMO. It usually represents a radical change for upstream though, the thought of not duplicating fonts all over the place is usually a foreign one. If this specific font is needed you can file a bug asking for ttf-aenigma to be split up, perhaps into ttf-aenigma-core and ttf-aenigma. The -core package could contain only the fonts other packages need to depend on and the main package could depend on the -core package. Other ways of splitting could be considered too if possible. There is precedent for this with ttf-dejavu packages: http://packages.debian.org/search?keywords=ttf-dejavu You could also ignore the lintian warning and have a beer :) Sometimes it is just not possible to satisfy lintian in a nice way. For example, for nsis I install stuff into the mingw32 lib/include dirs, which are not FHS compliant because the FHS doesn't deal with multi-arch yet. Here you might want to watch ttf-aenigma for changes to your font, in this case I don't see ttf-aenigma's chumby changing a whole lot though. Perhaps lintian does need to reduce the severity to wishlist/info for cases where the font package itself is quite large, say over 5MB. I don't think the right thing to do is add an override, unless perhaps the font is a fork of the ttf-aenigma version. In this case, rather than adding an override, I would suggest renaming the file and then splitting it out into ttf-aenigma-chumby-serendipity or something instead of keeping it in the serendipity package. Obviously merging these forks upstream would be a good idea too. -- bye, pabs http://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part