Bug#803790: fakeupstream.cgi: New Google Fonts upstream
On Tue, Nov 3, 2015 at 3:43 AM, Gioele Barabucci wrote:
> Before explaining the patch I need to explain why this is needed and the
> unusual way fonts on Google Fonts are "released". To start with, fonts made
> available on Google Fonts lack proper release tarballs. Each font is
> maintained in a subdirectory that is part of a huge git repository hosted on
> GitHub (previously on Google Code).
Could you contact the Google Fonts people? Maybe they could move to
more traditional release processes so that your patch is no longer
nessecary? Maybe they could move binary files to zip/tar files
attached to the github releases feature on the source repositories.
The person to contact about this is Dave Crossland <dave@lab6.com>.
https://github.com/googlefonts/
--
bye,
pabs
https://wiki.debian.org/PaulWise
Reply to: