Bug 240407
| Summary: | print/lilypond-devel: Fix fontforge version check | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Martin Neubauer <m.ne> | ||||||
| Component: | Individual Port(s) | Assignee: | Niclas Zeising <zeising> | ||||||
| Status: | Closed FIXED | ||||||||
| Severity: | Affects Many People | CC: | zeising | ||||||
| Priority: | --- | Keywords: | needs-qa | ||||||
| Version: | Latest | Flags: | m.ne:
maintainer-feedback+
koobs: merge-quarterly? |
||||||
| Hardware: | Any | ||||||||
| OS: | Any | ||||||||
| Attachments: |
|
||||||||
Created attachment 207275 [details]
fixed version check
removing BROKEN statement added between creating and submitting the previous patch
Part of the issue is that fontforge is stupid and tries to open a GUI before parsing options, such as -version, which doesn't need a GUI. I've submitted a RP for fontconfig for that issue. This looks like a good interim solution, though. There is no need to merge it to the Q3 branch, since it's only an issue after the fontforge update. A commit references this bug: Author: zeising Date: Mon Sep 9 16:54:33 UTC 2019 New revision: 511648 URL: https://svnweb.freebsd.org/changeset/ports/511648 Log: print/lilypond-devel: Fix configure Fix configure script issues detecting fontforge after fontforge update. PR: 240407 Submitted by: m.ne@gmx.net (maintainer) Changes: head/print/lilypond-devel/Makefile head/print/lilypond-devel/files/patch-configure Committed, thanks! |
Created attachment 207274 [details] fixed version check With the latest update to print/fontforge the version check didn't work anymore. The attached patch changes that check to extract the correct version again.