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#56268 - [firefox] Update PKGBUILD to use best practice calling of python2 binary
Attached to Project:
Arch Linux
Opened by Vorbote (vorbote) - Tuesday, 07 November 2017, 15:51 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 28 April 2019, 09:59 GMT
Opened by Vorbote (vorbote) - Tuesday, 07 November 2017, 15:51 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 28 April 2019, 09:59 GMT
|
DetailsAs per
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Linux_Prerequisites#Python the correct way to force the build system to use the needed python2 binary is by adding the following to .mozconfig (note that Arch Linux is mentioned explicitly): mk_add_options PYTHON=/usr/bin/python2 Please find attached a proposed patch. |
This task depends upon
best_practices_python2_define...
How can you possibly think this is "A non-essential functionality does not work, UNIX standards not respected, etc."???
...
I'm not even sure why anyone should care, this works just fine either way... and in fact the same Mozilla documentation does not even recommend either one, despite mk_add_options being arguably cleaner yet still lacking in objective superiority.
Neither the existent hack nor my proposed hack are needed in the PKGBUILD.