Well, let me know if that's the case! After all, my submission is almost identical as the existing packages such as font-ibm-plex and font-inconsolata?

I would prefer not to "fork" as another repository if I can avoid it!

-Yasu

On Sun, 2021-01-10 at 07:28 -0500, Julien Lepiller wrote:
I might be wrong, but I thought fonts were considered non-functional data. If that's the case, isn't cc-by-nc-nd acceptable?

Le 10 janvier 2021 05:38:16 GMT-05:00, Leo Prikler <leo.prikler@student.tugraz.at> a écrit :
Hi Yasu,


I don't think it'll be so simple.  It appears, that nerd-fonts already

includes – or at least has the potential to include – some non-free

glyphs, which would in turn then be part of Cascadia.  An instance

would be pomicons [1], which are licensed as CC BY-NC-ND.  A reviewer

would first have to verify, that Cascadia is indeed wholly covered

under the OFL or at least under a set of free licenses.


Yes, it sucks having to put that much effort into packaging a font, but

if you just want to have a workable font for programming, there are

probably better solutions than Cascadia, some of which are already

packaged in Guix – e.g. font-fira-code.


Regards,

Leo


[1] 
https://github.com/gabrielelana/pomicons


Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo:

Thank you for your comments!


Because I don't have a lot of time, is it ok to just re-format the

original submission, get it committed with the comment that the

package needs to be compiled rather than copied, when someone (or I)

wants to so properly?


Cheers,

Yasu



On Jan 10, 2021, at 18:16, Leo Prikler <

leo.prikler@student.tugraz.at> wrote:


Hello Vincent,


there is no .tar of the fonts however, that's a source tarball

generated by github.  To be fair, one should probably build this

font

(and other fonts) from source instead.  In particular, we might

want to

package nerd-fonts[1] first, since Cascadia appears to be an

iteration

of it.


Regards,

Leo


[1] 
https://github.com/ryanoasis/nerd-fonts