Red Hat Bugzilla – Bug 1258542
Review Request: hack-fonts - A typeface designed for source code
Last modified: 2017-05-21 15:30:43 EDT
Spec URL: https://heliocastro.fedorapeople.org/hack-fonts.spec
SRPM URL: https://heliocastro.fedorapeople.org/hack-fonts-2.010-1.fc22.src.rpm
Description: A typeface designed for source code
Fedora Account System Username: heliocastro
From the policy: "Fonts SHOULD be built from source whenever upstream provides them in a source format" - upstream does appear to provide source here.
They have the source, but no instructions how to build it whatsoever.
I just followed the same process used on Overpass Red Hat font, which has the source available, but same way, only the type faces are included.
NEW version released.
(In reply to Helio Chissini de Castro from comment #2)
> They have the source, but no instructions how to build it whatsoever.
> I just followed the same process used on Overpass Red Hat font, which has
> the source available, but same way, only the type faces are included.
This is ridiculous, the fonts are derived from DejaVu, and DejaVu build is completely scripted. The project just need to fork the build scripts like it forked everything else, and decide on a naming policy
I really hope to see this package in the main repo soon :)
Where are we in this review? Upstream is excited to get Hack into Fedora.
Updated SPEC and SRPM
Copr repo updated as well
Any further update on this?
Package request has been denied with the reason: Review not approved.
I will do review since I want this font already. Expect a review for tomorrow.
I'll just take this over if nobody is doing this, will ask for a review.
This was strangely forgotten.
Before we can even move to package this, does anyone know how this is built? I've opened a ticket on upstream's github, Debian has this packaged but I don't see them doing any source builds of the fonts.
I need some clarification on our policy for this. Given Debian is even more severe for requiring sources, maybe Fedora should follow Debian's guide on this?
Debian is using same approach as me, using the precompiled ttf/otf
The only thing is that we're deploying only ttf and debian both ones.
And i personally don't know if worth pack the web fonts.
Well, if it's acceptable to Debian surely this should be acceptable to Fedora, if not something seems wrong with our policy...
Debian is not inevitably 'freer' than Fedora. Our requirements are more strict in some ways. Just because Debian doesn't (and, AFAICT, never has) required fonts to be compiled from source doesn't mean we're wrong in requiring this.
Upstream bug regarding building this font from source: https://github.com/chrissimpkins/Hack/issues/227
I am in contact with upstream, they are looking at improving our ability to build the fonts from scratch. More on this when they get back to me.
The Hack license is now acceptable for Fedora:
Also, FWIW I could really use the web fonts for Bodhi (which is why I wanted to package Hack) so I would appreciate if you could include a subpackage with those files.
I'm willing to review this package if nobody else has a "claim" on reviewing it.
After reading the scrollback it does sound like Shawn is lined up to do the review so I'll defer, but I'm happy to be a standin. I'll memorize my lines.
My interpretation of the packaging rules is that SHOULD != MUST when it comes to building the font from source. The font guidelines do use the word "MUST" in other places so I take that to mean that this shouldn't block the package from getting into Fedora. It's obviously better if we build the font from source, but since there isn't a clear way to do that provided by upstream I don't think we have to wait for https://github.com/chrissimpkins/Hack/issues/227 to be solved to get this into Fedora. I would recommend allowing the package in with the OTF files (and hopefully web files for me ☺) and then filing a BZ to build from source if possible later.
Well, there's still the *general* packaging guidelines to consider. I don't think the font guidelines supersede those, in fact the section on packaging from source specifically references back to them. And they're quite specific about when you get an exception from the requirement to build from source.
I've poked Chris on twitter, you can certainly help with packaging, it's always good to have co-maintainers.
Adam, fair enough.
Shawn, if you don't want to deal with the web files I'd be happy to handle that part as a co-maintainer.
Here is the tool can use to build the fonts
We will need this packaged too as a dependency for building, if we want to build them now.
Any news here?
I should have something soon, i'll put up a .spec for review this week.