Le jeudi 02 mars 2023 à 02:26 +0100, Jean Abou Samra a écrit : > Folks, > Maybe we should go over all packagers of LilyPond and check that they have > accounted for the change that made the build system no longer install text > fonts? Homebrew [got it > wrong](https://github.com/Homebrew/homebrew-core/issues/119476) (and it took > effort to convince them that this was not a LilyPond bug!), Debian [got it > wrong](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026200#55) before > Jonas flagged the problem, and now I have noticed that MacPorts [got it > wrong](https://trac.macports.org/ticket/67026#ticket) as well.
So, I did some digging and here is what I found: Fedora and Gentoo seem to get it right. ArchLinux gets it almost right, however I think that TeX Gyre fonts should be made required, [https://bugs.archlinux.org/task/77700](https://bugs.archlinux.org/task/77700). Manjaro takes the package from ArchLinux. Debian also made the fonts-texgyre package optional. I've opened [https://gitlab.com/lilypond/lilypond/-/merge_requests/1855](https://gitlab.com/lilypond/lilypond/-/merge_requests/1855) to document that they should be required and posted about this on [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026200](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026200) (should appear soon). Linux Mint and openSUSE does not package LilyPond. openSUSE has "community packages" for it but I didn't look at them. Chocolatey still has LilyPond 2.22, Homebrew was fixed, MacPorts has a bug page.
signature.asc
Description: This is a digitally signed message part
