[Pkg-nginx-maintainers] Bug#843777: Bug#843777: temporarily loosen new nginx modules ban until separate module compilation available?
Michael Lustfield
michael at lustfield.net
Mon Feb 20 18:20:29 UTC 2017
On Mon, 20 Feb 2017 13:31:18 +0100
Mark Van den Borre <mvandenborre at fosdem.org> wrote:
> I did some further research.
>
> https://www.nginx.com/blog/dynamic-modules-development/ and specificly
> https://www.nginx.com/blog/dynamic-modules-development/#comment-3165213773
> clearly indicate that no progress should be expected from nginx on
> further independence of nginx module compilation from the main nginx
> source tree.
That first response you got is a little bit of a bummer to read, but it also
indicates we /might/ /maybe/ actually be able to finally get somewhere.
> Could you clarify what the goal is you are working towards? Is there
> any place where help might be useful on this trajectory?
If you have experience with debian packaging, you can discuss an idea with us
in #debian-nginx on oftc.
> If you were us, absent any "go" for inclusion into Debian, what would
> you do? Currently thinking here is to produce a dyn load
> nginx-rtmp-module Debian package compiled against the Debian nginx
> source package. We'd have to host it outside Debian, of course :-( ,
> but it seems like this would keep us as close to Debian as possible,
> and maximise the chances for future inclusion.
This actually isn't a bad idea, but maybe we can start off with the inclusion?
--
Michael Lustfield
More information about the Pkg-nginx-maintainers
mailing list