Page MenuHomeSolus

Split font-firago in ttf/otf packages
ClosedPublic

Authored by kyrios123 on Jul 27 2021, 5:27 PM.
Tags
None
Referenced Files
F11072857: D11537.diff
Sat, Aug 12, 2:38 AM
F10907338: D11537.id.diff
Jul 6 2023, 7:18 PM
F10793726: D11537.id27910.diff
May 27 2023, 12:48 PM
F10793481: D11537.id28060.diff
May 27 2023, 11:30 AM
F10793434: D11537.id27913.diff
May 27 2023, 11:22 AM
F10793287: D11537.diff
May 27 2023, 10:46 AM
F10778367: D11537.id27910.diff
May 24 2023, 7:17 AM
F10760455: D11537.id27913.diff
May 18 2023, 1:17 AM
Subscribers

Details

Summary

Reference task T9816

Signed-off-by: Pierre-Yves <pyu@riseup.net>

Test Plan

Install otf package then orignal (ttf) package to validate conflict

Diff Detail

Repository
R4565 font-firago
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Feedback on this:

  • I think it is reasonable to allow for both to be installed. Some graphics applications make better use of OTF vs TTF, and vise-versa. Given the font is niche enough, I would like to think people that choose one or the other may be able to understand what best works for their usecase.
  • We could probably do with patterning TTF files into font-firago-ttf and doing a replaces of font-firago to font-firago-ttf. We can keep the same "main" (so not renaming the name in package.yml itself), we just aren't producing a package for it, similar to what we do for LibreOffice.

Implement requested changes

@JoshStrobl Should I deprecate the font-firago package ?

I can handle the deprecation :)

This revision is now accepted and ready to land.Aug 5 2021, 4:58 PM
This revision was automatically updated to reflect the committed changes.