[haikuports] SOURCE_URI for Noto fonts 404

["Humdinger" (Redacted sender "humdingerb" for DMARC)]

Hi there,

I'm looking into the noto fonts recipes and discovered that the old
URI https://www.google.com/get/noto/pkgs/NotoSans-hinted.zip isn't
valid anymore.
Looks like you can only download all fonts packed together, a whooping
472MiB zip!

One solution would be to get the particular fonts directly from their
github at https://github.com/googlei18n/noto-fonts
The downside is, that this means that their checksum keeps changing
(as was recently discovered with the gyp package).
So... do we just drop the checksum altogether?
If so, should we simple always get the master or do we get a specfic commit?

Or should we just grab the fonts and host them on HaikuArchives?
Any better ideas?

Regards,
Humdinger

--
Did you know:
If half the Haiku supporters at http://www.goodsearch.com
made 10 searches a day, we could have a fulltime developer.

[Adrien Destugues]

Post by "Humdinger" (Redacted sender "humdingerb" for DMARC)
Hi there,
I'm looking into the noto fonts recipes and discovered that the old
URI https://www.google.com/get/noto/pkgs/NotoSans-hinted.zip isn't
valid anymore.
Looks like you can only download all fonts packed together, a whooping
472MiB zip!

This seems to work here?

https://noto-website.storage.googleapis.com/pkgs/NotoSans-unhinted.zip

Post by "Humdinger" (Redacted sender "humdingerb" for DMARC)
One solution would be to get the particular fonts directly from their
github at https://github.com/googlei18n/noto-fonts
The downside is, that this means that their checksum keeps changing
(as was recently discovered with the gyp package).

github does not have this problem. gyp is still hosted on some Google
internal service, and that service has changing checksums if you
download a zip of a specific commit (with many files). There are no
problems when downloading a single file.

The changing checksum happens because the service hosting gyp generates
the zip archive on the fly when someones requests it, and the code they
use to generate the zip makes slight changes to the archive (file
content is the same, but creation dates changes, for example). github
took care of avoiding such problems, and their zip archives are always
bit-for-bit identical.


Anyway, I think a single "noto" recipe could download all the fonts in
the huge zipfile, then generate multiple packages from it (noto_sans,
noto_serif, etc), just like we do for _devel packages in most recipes.

["Humdinger" (Redacted sender "humdingerb" for DMARC)]

Post by Adrien Destugues
This seems to work here?
https://noto-website.storage.googleapis.com/pkgs/NotoSans-unhinted.zip

Right, that one does. Thanks!

[changing checksums]

Post by Adrien Destugues
github does not have this problem.

It does, too. I downloaded
https://github.com/googlei18n/noto-fonts/blob/master/hinted/NotoSans-Regular.ttf
twice. One time I get sha256sum of
f5f858cbc14af2276fd9784c6a44f07c6e158d2696c90b34c99a3c12415a3812, next time
7fe5c03fddee3b1319d6abd826b751b3931b7321bc1c161ba3abe69bcea405b8.

Post by Adrien Destugues
Anyway, I think a single "noto" recipe could download all the fonts in
the huge zipfile, then generate multiple packages from it (noto_sans,
noto_serif, etc), just like we do for _devel packages in most recipes.

This seems to be the best solution. I'll try that, thanks!

Regards,
Humdinger

--
Did you know:
If half the Haiku supporters at http://www.goodsearch.com
made 10 searches a day, we could have a fulltime developer.

[Adrien Destugues]

Post by "Humdinger" (Redacted sender "humdingerb" for DMARC)

Post by Adrien Destugues
This seems to work here?
https://noto-website.storage.googleapis.com/pkgs/NotoSans-unhinted.zip

Right, that one does. Thanks!
[changing checksums]

Post by Adrien Destugues
github does not have this problem.

It does, too. I downloaded
https://github.com/googlei18n/noto-fonts/blob/master/hinted/NotoSans-Regular.ttf
twice. One time I get sha256sum of
f5f858cbc14af2276fd9784c6a44f07c6e158d2696c90b34c99a3c12415a3812, next time
7fe5c03fddee3b1319d6abd826b751b3931b7321bc1c161ba3abe69bcea405b8.

Because you downloaded the master, which changes each time there is a
commit. This is why we need to point to a specific commit/tag to make sure
the file doesn't change.

Otherwise, you don't know what you're downloading. Maybe someone took
over the git repo and broke everything? Or maybe they started using a
new font file format and our freetype can't render it anymore? Anything
could happen, and it's important to know when the file changes.

["Humdinger" (Redacted sender "humdingerb" for DMARC)]

Post by Adrien Destugues
Because you downloaded the master, which changes each time there is a
commit.

You're right. I thought I specified a commit when testing, but
apparently didn't. Trying with this works:
https://github.com/googlei18n/noto-fonts/blob/3dfd3e923e661c1bdd95ecacc04394c3e35d119e/hinted/NotoSans-Italic.ttf

Regards,
Humdinger

--
Did you know:
If half the Haiku supporters at http://www.goodsearch.com
made 10 searches a day, we could have a fulltime developer.