algaos/algaos-ebuild-tree/eclass/nginx.eclass, branch next

nginx{,-module}.eclass: Pass --as-needed before libraries

2026-09-16T00:09:45Z

Signed-off-by: Peter Volkov Part-of: https://codeberg.org/gentoo/gentoo/pulls/1621 Signed-off-by: Sam James

nginx.eclass: avoid duplicates in saved configure flags (keepwork)

2026-09-16T00:09:44Z

Signed-off-by: Peter Volkov Part-of: https://codeberg.org/gentoo/gentoo/pulls/1621 Signed-off-by: Sam James

nginx{,-module}.eclass: save NGINX build config by storing ./configure flags

2026-07-31T20:27:43Z

Background ========== NGINX's ABI and API can change depending on supplied ./configure flags (most notoriously, enabling/disabling many first-party modules can change ABI and API of NGINX as a whole). Perhaps unrelated, but third-party modules are expected to be built in-tree, at the same time NGINX is built. It is because of these two factors that we have to freeze/preserve NGINX configuration. Configuration-saving methods ============================ In general, I have identified two approaches as to how to preserve NGINX configuration for building third-party modules out-of-tree. The current implementation saves the generated headers: ngx_auto_config.h and ngx_auto_headers.h. When third-party modules are built, the ./configure flags are mostly ignored. It is straightforward and easy and allowed us to cut some parts of configuration out. Unfortunately, due to headers not being first-class configuration in the build system, it has proven to be quite difficult to change some parts of the build using headers alone. For instance, my initial header-mangling-based implementation of ngx_force_module (see the following commit) proved to be quite limited and not really robust. The reason why I used this approach initially is because when nginx-module.eclass was written, none of the ngx_force_module fancy crossed my mind. Second method is saving the ./configure flags themselves. Although increasing the src_configure time (since we no longer skip phases), this allows to build modules and edit the build configuration more easily and correctly. This also gives users/ebuild authors more control since, as stated above, most ./configure flags are ignored in the header implementation. Compatibility ============= While nginx.eclass completely removes support for emitting ngx_auto_{config,headers}.h, generating only ./configure flags, nginx-module.eclass will support both configuration-saving methods for the time being, allowing users to update www-servers/nginx. Notes ===== Passing ./configure flags around makes modules transitively depend on NGINX's dependencies. -Wl,--as-needed is added to LDFLAGS since NGINX links external libraries needed by first-party modules also to third-party modules. Signed-off-by: Zurab Kvachadze Part-of: https://codeberg.org/gentoo/gentoo/pulls/1329 Signed-off-by: Sam James

nginx.eclass: fix http_uwsgi test dependency on uwsgi[ssl]

2026-07-31T20:27:42Z

If http_ssl and http_uwsgi are used together, NGINX runs some tests that use SSL functionality of UWSGI. This commit changes the http_uwsgi test dependency to depend on uwsgi[ssl]. We could have opted for a more complex nginx_module_http_ssl-gated dependency, but this is simple and it works. Closes: https://bugs.gentoo.org/977774 Signed-off-by: Zurab Kvachadze Part-of: https://codeberg.org/gentoo/gentoo/pulls/1329 Signed-off-by: Sam James

nginx.eclass: src_install(): add missing dies for sed

2026-07-31T20:27:36Z

Signed-off-by: Zurab Kvachadze Part-of: https://codeberg.org/gentoo/gentoo/pulls/1329 Signed-off-by: Sam James

nginx.eclass: avoid heredoc in global scope incurred by NGINX_UPDATE_STREAM

2026-07-11T19:35:16Z

Also, avoid a useless-use-of-has and improve the language of the diagnostic, the content of which remains shorter than 80 characters. As noted by a bug comment, this also addresses the issue that the QA warning being issued was hitherto empty. Acked-by: Zurab Kvachadze Closes: https://bugs.gentoo.org/979047 Signed-off-by: Kerin Millar Signed-off-by: Sam James

nginx.eclass: avoid heredoc in global scope

2026-07-10T16:44:51Z

A heredoc may cause the use of a temporary file with < EAPI 9 and even then still with >= EAPI 9 if the input is large. This becomes a problem if sandboxing is applied to metadata generation. Closes: https://bugs.gentoo.org/978940 Signed-off-by: Sam James

nginx.eclass: unslot NGINX, slotmove all slots to :0

2026-07-01T11:26:56Z

This has been a recurring source of nasty bugs and issues. Bugs aside, we should not abuse slots as abstract tags to select to the world file. This commit makes the eclass assign only SLOT="0/${PV}", irrespective of NGINX_UPDATE_STREAM. Also, 'stable', 'mainline' and 'live' SLOTs are slotmoved to '0'. Bug: https://bugs.gentoo.org/977755 Closes: https://bugs.gentoo.org/959569 Signed-off-by: Zurab Kvachadze Part-of: https://codeberg.org/gentoo/gentoo/pulls/1277 Merges: https://codeberg.org/gentoo/gentoo/pulls/1277 Signed-off-by: Sam James

nginx.eclass: Support EAPI 9

2026-02-20T19:09:35Z

In EAPI 9, NGINX_SUPPORT_MODULE_STUBS is enabled unconditionally. Signed-off-by: Zurab Kvachadze Signed-off-by: Sam James

nginx.eclass: Support /etc/nginx/modules-{available,enabled}

2026-02-20T19:09:34Z

This directory layout allows for more flexible dynamic module management. nginx-module.eclass generates `load_module` .conf stubs for every module and installs them into /etc/nginx/modules-available. Then, modules can be enabled or disabled by adding or removing symlinks from /etc/nginx/modules-enabled to /etc/nginx/modules-available, potentially with an eselect module. See bug 967022 for background information. This commit adds a new eclass variable NGINX_SUPPORT_MODULE_STUBS that must be turned on to create the directories and add the include into shipped nginx.conf. Also, the live NGINX version is bumped setting the new variable. Bug: https://bugs.gentoo.org/967022 Signed-off-by: Zurab Kvachadze Signed-off-by: Sam James