Le mardi 27 mars 2007 à 22:26 -0700, Toshio Kuratomi a écrit : > If the font is removed, then the config file has to be updated. But the > thing is that the user intiates all of these actions. Bzzt - when you bundle lots of different fonts in a single package the user can't control fonts at the rpm level, since the bundle will always exist but with different contents (that's a big problem with fonts-region packages) - if these things take legacy core fonts strings the string associated to a font has been known to change even though the font itself was still shipped - also some core font users (most notably X) will crash if these aliases do not resolve. So a small change a user may have forgotten about will kill his system months later if config(noreplace) is used and an old stale config file is kept on the system - core fonts need to die die die. robust config is better than perfect brittle config in core fonts case -- Nicolas Mailhot
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers
-- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly