|Summary:||New port: x11-fonts/urw-core35-fonts URW core35 fonts in various formats|
|Product:||Ports & Packages||Reporter:||m.ne|
|Component:||Individual Port(s)||Assignee:||Fernando Apesteguía <fernape>|
|Severity:||Affects Some People||CC:||fernape|
|Bug Depends on:|
Description m.ne 2020-12-03 12:34:50 UTC
Created attachment 220214 [details] Patch adding new port x11-fonts/urw-core35-fonts This new port is a prerequisite to changes I intend to make to print/lilypond(,-devel). The background is lilypond's move from TeX Gyre to URW as default text fonts (see https://gitlab.com/lilypond/lilypond/-/issues/6002 for details.) The lilypond build system assumes different font files than provided by the already existing ports. I modelled the new port on the one from MacPorts (see https://github.com/macports/macports-ports/blob/master/x11/urw-core35-fonts/Portfile), however I am unsure whether installing all formats is actually desirable as opposed to just having the .otf files required by lilypond. Thus I'd like to discuss this before having the port committed and if the latter option is considered the right approach I'd happily modify the patch accordingly.
Comment 1 Fernando Apesteguía 2020-12-23 07:53:19 UTC
Hi there, So if I understand this correctly, print/lilypond-devel will not work with the fonts in print/ghostscript9-agpl-base for example? On the other issue, I would install all formats and not just the .otf. Or if the resulting package is too big, maybe make the available formats optional (with otf being the default).
Comment 2 m.ne 2020-12-23 10:19:04 UTC
(In reply to Fernando Apesteguía from comment #1) Hello, Thank you for your comments. At least for now lilypond still requires the TeX Gyre fonts (from ghostscript) and uses those as preferred fallback. Only if those aren't present (which can't really happen if the package is installed properly) the system defaults for the serif/sans serif/monospace families are used. My concern is mainly that as general usage moves to newer lilypond versions, the results should match across os boundaries. Concerning the different font formats, the installed package adds up o ~17MB. This includes all typefaces, not just those lilypond uses. To me this doesn't look unreasonably huge, so unless someone else chimes in with some other arguments I'll keep the proposed port as is.
Comment 3 Fernando Apesteguía 2020-12-23 10:38:18 UTC
(In reply to m.ne from comment #2) Make sense to me and also 17 MB seems reasonable these days. One more comment: is there any other MASTER_SITES that do not scare people away? :) I see audio/libtrermor uses a similar MASTER_SITES, but I wonder if there is another one (I couldn't find it myself).
Comment 4 m.ne 2020-12-23 11:52:29 UTC
(In reply to Fernando Apesteguía from comment #3) https://gitlab.com/lilypond/lilypond/-/issues/6002 suggests there used to be a more standard source (https://github.com/URWTypeFoundry/Core_35). However, that repository and its owner have vanished by now, probably in connection with the takeover of URW by Monotype. So, scary or not, it looks like we're stuck with that MASTER_SITE for now.
Comment 5 commit-hook 2020-12-23 14:47:33 UTC
A commit references this bug: Author: fernape Date: Wed Dec 23 14:47:21 UTC 2020 New revision: 558995 URL: https://svnweb.freebsd.org/changeset/ports/558995 Log: New port: x11-fonts/urw-core35-fonts URW core35 fonts in various formats. This port is not the same as x11-fonts/urwfonts as they install different files and different formats. This port is needed for the upcoming version update of print/lilypond-devel PR: 251560 Submitted by: email@example.com Changes: head/x11-fonts/Makefile head/x11-fonts/urw-core35-fonts/ head/x11-fonts/urw-core35-fonts/Makefile head/x11-fonts/urw-core35-fonts/distinfo head/x11-fonts/urw-core35-fonts/pkg-descr head/x11-fonts/urw-core35-fonts/pkg-plist
Comment 6 Fernando Apesteguía 2020-12-23 14:48:04 UTC