Thanks in advance!
I already looked into it. Unfortunately upstream changed their release artefacts, no longer providing the ready-to-use font files in the source archive. So I have to rework the ebuild to build the font files locally, which will take some time to make it work.
Just that you know it will take a bit of time.
No worries and thanks for the update... I can always install it manually to ~/.fonts, but it's nice to automatically get updates across all my machines.
*** Bug 703422 has been marked as a duplicate of this bug. ***
This is unfortunately even more difficult than I initially anticipated.
Before this version, upstream published a source archive with both the sources and the compiled font files. This was easy to package.
Unfortunately, upstream changed this, now there is a source archive with the sources only and separate per-file downloads for the compiled font files.
This leaves two options: Either download each file individually (which is not really a good style and also introduced questions about how these files should be named, so they can be cached etc.) or download the source archive and build the font files from source.
I intended to do the latter one (also after advice from #proxy-maintainers on IRC). Though even as the build script is completely in Python and straight forward, it unfortunately depends on a number of Python packages currently not in-tree. I do not have the time or motivation to add and maintain a number of additional Python packages. Also in the mean time I learned from upstream's build instructions (https://github.com/microsoft/cascadia-code/wiki/Modifying-Cascadia-Code#building-the-font-from-source) that building from source would result in font files without the hinting information, which is build using a Windows only application.
So now I am stuck as both ways are blocked. If there is anyone willing to help, I would appreciate. Meanwhile there is an upstream issue asking to include the font files again into the archive (https://github.com/microsoft/cascadia-code/issues/208), but it currently does not look like there is any activity about that.