Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#65845 - [lilypond] Cleanup PKGBUILD
Attached to Project:
Community Packages
Opened by Jonas Hahnfeld (hahnjo) - Sunday, 15 March 2020, 21:05 GMT
Last edited by Antonio Rojas (arojas) - Monday, 16 March 2020, 08:13 GMT
Opened by Jonas Hahnfeld (hahnjo) - Sunday, 15 March 2020, 21:05 GMT
Last edited by Antonio Rojas (arojas) - Monday, 16 March 2020, 08:13 GMT
|
Details(actively contributing upstream, let me know if you have questions)
I would recommend to update PKGBUILD as attached. In particular, this avoids https://bugs.archlinux.org/task/65789 by passing --disable-documentation instead of patching configure.ac and running ./autogen.sh (which also invokes the generated ./configure with the wrong default prefix /usr/local). Making 'python2' an optdepend is clearly debatable, but I'd argue that it's not needed for running lilypond itself. |
This task depends upon
Closed by Antonio Rojas (arojas)
Monday, 16 March 2020, 08:13 GMT
Reason for closing: Fixed
Additional comments about closing: lilypond 2.20.0-3
Monday, 16 March 2020, 08:13 GMT
Reason for closing: Fixed
Additional comments about closing: lilypond 2.20.0-3
Comment by Jonas Hahnfeld (hahnjo) -
Sunday, 15 March 2020, 21:40 GMT
No sorry, --disable-documentation also skips man and info pages (I thought it only influenced the online documentation). The attached PKGBUILD restores the patching, but calls ./autogen.sh with --noconf.
PKGBUILD