1. Please split the package so different upstreams with different licenses and
different levels of unicode compliance are not mixed toguether
(esp. since http://www.mozilla.org/projects/mathml/fonts/ now recommends *not*
installing some of them)
2. Please make sure the result is conformant with the latest font packaging
guidelines and current fc-cache behaviour
3. Please document the result on
See also this wishlist item
Nod, such cleanups have been a long-standing todo item of mine. Still
pondering the best approach to take here.
1 make each upstream a subpkg
2 kill mathml-fonts altogether, package each upstream separately
3 some combo of 1 and 2
Obviously, I prefer do-it-all-cleanly option 2, but since you're the one doing
the work, that's your choice
The more I look at it, the more 2 seems to be the only sane option here. Will commence working on split items.
*** Bug 477423 has been marked as a duplicate of this bug. ***
mailed owners of packages with deps on mathml-fonts, including koffice, lyx, abiword, for details on what specifically is required by each of them.
In the near future, I'll EOL mathml-fonts, and potentially resurrect anything still needed.
lyx-fonts pkg submitted for review, bug #514549
At least LyX is also available on EPEL and AFAIK the modern style font packages work only on >= F11 thanks to a series of mutually incompatible policy changes in the past.
What's the workaround for EPEL? Do you stick with mathml-fonts in the current EPEL releases?
I'll make sure things stay compatible on the epel side of things, whether that means sticking with mathml-fonts as they are or incorporating something new, but compatible, is still unclear.
now build as part of lyx
* Mon Aug 03 2009 Rex Dieter <email@example.com> - 1.6.3-3
- add lyx-*-fonts subpkgs (#452357, #514549)
- -common (noarch) subpkg
- trim %changelog
TODO/FIXME remains to make lyx compatible with EPEL (in the absense of fontpackages-devel). Still pondering on how best to do that. May end up doing the font management by hand, not relying on fontpackages-devel at all.... not sure.
(In reply to comment #10)
> TODO/FIXME remains to make lyx compatible with EPEL (in the absense of
> fontpackages-devel). Still pondering on how best to do that. May end up doing
> the font management by hand, not relying on fontpackages-devel at all.... not
fontpackages can probably be imported directly in EPEL if you need it, at worst you'll have to tweak the spec templates so they don't use stuff like noarch subpackages. The only hard dep of fontpackages is rpm (also if fontconfig is too old it won't autogenerate font metadata but then there's probably nothing to use it it EPEL either right now)
lyx-1.6.4-1.fc11,koffice-1.6.3-24.20090306svn.fc11 has been submitted as an update for Fedora 11.
lyx-1.6.4-1.fc10 has been submitted as an update for Fedora 10.
lyx-1.6.4-1.fc11, koffice-1.6.3-24.20090306svn.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
lyx-1.6.4-1.fc10, koffice-1.6.3-24.20090306svn.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
lyx-1.6.4-1.el5, koffice-1.6.3-24.20090306svn.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.