Red Hat Bugzilla – Bug 121099
RFE: separate source package for fonts.
Last modified: 2007-11-30 17:10:40 EST
Would it be possible/reasonable/desirable to split the xorg-x11
_source_ package into separate packages for fonts and binaries?
Currently, any update/errata/etc in the xorg-x11 would case new font
packages to be built and distributed (and some of those are pretty
big). If they were made separate, this would not be the case.
Absolutely agreed 200%. I've been wanting to do that for quite some
time now. I actually split out the pcf fonts before in an attempt
to do this, but ended up with a build loop because the font-utils
need to be built first in order to build the fonts, and the fonts
are needed in order to build the monolithic build with fixed/cursor
built in. There was some other issue I don't remember specifically
also, as it's been some time now since I investigated this.
With promises from upstream that the pcf fonts would be going away
very soon, to be replaced with .TTF fonts with embedded bitmaps,
it seemed it might be wasted effort to fix the problems above, if
it would be short lived anyway. Now however, there have been
3 major X releases in which still ship with PCF fonts. The TTF code
is now present, but there are some conversion utilities missing,
and other issues preventing the switchover.
I'd really like to switch to TTF based fonts as soon as possible,
as that would mean we could eliminate any loop problems, but
unfortunately there's no guarantee of when that will actually
happen, although it is being worked on upstream, which is good for
some point in the future.
Since this is indeed a major issue, IMHO at least though, I do not
think we should wait any longer for the TTF bitmap fonts from
upstream. I think what I am going to do instead, is to extract
all of the fonts from a monolithic build, tarball them up, and then
use _that_ as the source tarball for a src.rpm to spit the fonts
back out into the same-named packages we currently ship.
That essentially means that fonts get generated once, and can also
be noarch packages. The only downside I know of about this, is that
PCF fonts are generated based on the endian of the CPU creating them,
and that they are slightly slower on opposite-endian CPUs, although
I am told this is not a problem on modern systems anyway, and that
TTF fonts are all big-endian data anyway, and that's what the long
term goal is.
Summary: I fully agree with your suggestion, and think it is a
good idea to implement one solution or another in the Fedora Core 3
timeframe for sure.
Thanks for logging in bugzilla.
Fonts are now produced from the fonts-xorg rpm for Fedora devel.
Setting status to RAWHIDE.