Hey there,
a while back Jonas Licht (Cc) wrote an eclass for Nginx dynamic modules.
For a few years now, Nginx supports building third party dynamic modules outside of the Nginx source tree with the help of Nginx's build system.
Since this involves quite some work to obtain information from the Nginx build configuration and using Nginx's build system to actually build the module, an eclass was written. The last RFC didn't make it into
::gentoo, since the requested changes haven't been applied.
However, we have been working on the eclass again and applied all the requested changes, made it EAPI=8 compatible and were able to use it successfully to package a third party Nginx module in ::fem-overlay [0].
This patchset contains the reworked nginx-module.eclass for building
third party modules using Nginx's build system as separate packages. Furthermore the category www-nginx is added where these third party
modules shall be put. Lastly, www-nginx/nginx-vod-module is added as a
first package using this eclass.
The patchset is also available as PR #16053 on GitHub [1]. If this
patchset is applied, the other PR for adding nginx-vod-module [2]
probably becomes obsolete [2].
How many packages do you expect to add to this new category? It's not customary to create a new category for one package.
How many packages do you expect to add to this new category? It'sWe currently have 24 third party modules in www-apps/nginx pulled in conditionally via USE flags. With nginx-module.eclass we should be
not customary to create a new category for one package.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (3 / 13) |
Uptime: | 06:19:56 |
Calls: | 10,388 |
Calls today: | 3 |
Files: | 14,061 |
Messages: | 6,416,810 |
Posted today: | 1 |