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#53378 - [nginx-mainline] Enable dynamic module compatibility
Attached to Project:
Arch Linux
Opened by Kevin Dodd (Jesin) - Sunday, 19 March 2017, 23:15 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Monday, 27 March 2017, 11:03 GMT
Opened by Kevin Dodd (Jesin) - Sunday, 19 March 2017, 23:15 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Monday, 27 March 2017, 11:03 GMT
|
DetailsStarting in version 1.11.5, nginx has a new configure option "--with-compat", which enables the executable to load new dynamic modules without being rebuilt.
Maxim Dounin (the upstream developer who signed the last release) recommends that package-maintainers enable this option: https://mailman.nginx.org/pipermail/nginx-devel/2016-October/008920.html Please add "--with-compat" to the "_mainline_flags" array in the PKGBUILD. 
nginx-mainline-with-compat.pa...
(0.2 KiB)
|
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Monday, 27 March 2017, 11:03 GMT
Reason for closing: Fixed
Monday, 27 March 2017, 11:03 GMT
Reason for closing: Fixed
I would also change the build to compile every possible module as dynamic.
Maybe it's time for a split pkgbuild?
Massimiliano, I don't see many advantages of this. Space savings will be minimal, and current stance is that we rather avoid unnecessary splits.
On the other hand, making the built-in modules dynamic allows the user to choose whether to enable them or not, so I still would like them to be dynamic if possibile.