Hi,

I have just noticed two potential problems in the fonts spec template.

Citing http://fedoraproject.org/wiki/Packaging/FontsSpecTemplate:

> Conflicts: fontconfig<xxx
>
> This directive will ensure concurrent fontconfig updating if
> your ruleset uses some new syntax fontconfig versions shipped
> in previous Fedora releases do not understand.
> Do not use a versioned Requires, as this will force fontconfig
> installation unconditionally.
> Resources like fonts must not force the installation of a
> particular handler.

The template's %post and %postun scriptlets run fc-cache from the fontconfig package.

Potential problem #1: Does "Conflicts: fontconfig<xxx" ensure that the conflicting fontconfig package is not installed at both %post and %postun time?

Potential problem #2: What happens if fontconfig is not installed, then a bunch of font packages are installed, and only then fontconfig is installed? The font packages' %post have had no chance to run. The analog problem occurs with %postun when the fontconfig package is uninstalled.

It's possible that both potential problems turn out not to be problems at all, but IMHO the docs should address them.

Uli

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Fedora-fonts-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-fonts-list

Reply via email to