https://bugzilla.redhat.com/show_bug.cgi?id=1807239

Nicolas Mailhot <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|[email protected]    |[email protected]
           Doc Type|---                         |If docs needed, set a value



--- Comment #1 from Nicolas Mailhot <[email protected]> ---
As written on the fonts list:

    I've submitted a new font package for review [1], but I have 0
    experience with fonts (I need it to unbundle it from [2]), and I found
    the documentation about font packages a little bit outdated. It's a
    pretty simple font (OFL, single family with a couple of styles),


We were aware of this, so it’s been rewritten, and FPC approved the rewrite two
weeks ago.
https://pagure.io/packaging-committee/issue/935

It’s not published yet, FPC is proofing the text, but you can already read the
pre-proofed version here using asciidoctor.js
https://pagure.io/packaging-committee/pull-request/934

APPLICABILITY

For a very simple font family like NewsCycle most of the twists of the document
won’t apply, you just need to use the new macros available in
fonts-?rpm-macros. fonts-rpm-templates in F32+ provides example spec templates.
Do read the parts on how to depend on font packages from non font packages,
however, you will use them.

That will simplify your spec quite a bit, and generate the fonts metainfo file
for you (I see you wrote one by hand, you can keep it if you like it, apologies
for being slow to update guidelines, and the needless manual work).

Once you’ve updated your spec to the new guidelines I will review it and help
you wrap it up.

TARGET RELEASES

The new font macros are available in F32, F33, and currently been pushed to
F31. The aim is to have all new packages use them for F31+, and convert
existing packages before F34 (at that point compatibility glue for previous
macros will be dropped). That will get us a single packaging target for all
supported Fedora releases soonish.

EL8 & EPEL

There is no plan short term to enable them for EPEL8, because the
redhat-rpm-config version here is too old and missing some common code.
However, an EL8 redhat-rpm-config refresh has already been requested to @rh
engineering by another SIG
https://bugzilla.redhat.com/show_bug.cgi?id=1774139

It would not take much to complete this refresh with the bits used by out fonts
macros, should anyone be interested (both packaging guidelines depend on pretty
much the same common code, there are a couple fonts-specific commits in
redhat-rpm-config Go does not need, but they are marginal)

I won’t drive EPEL-ing myself, but I will help anyone willing to take the
subject.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to