Date: Thu, 03 Dec 2020 12:34:50 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 251560] New port: x11-fonts/urw-core35-fonts URW core35 fonts in various formats Message-ID: <bug-251560-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251560 Bug ID: 251560 Summary: New port: x11-fonts/urw-core35-fonts URW core35 fonts in various formats Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: m.ne@gmx.net Created attachment 220214 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D220214&action= =3Dedit 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/60= 02 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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251560-7788>