Date: Thu, 4 Jun 2015 14:51:10 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Stuart Cardall <developer@it-offshore.co.uk>
Cc: alpine-aports@lists.alpinelinux.org
Subject: Re: [alpine-aports] [PATCH] testing/nginx-naxsi: update to 1.9.1
Message-ID: <20150604145110.27b650cd@ncopa-desktop.alpinelinux.org>
In-Reply-To: <1432951079-24456-1-git-send-email-developer@it-offshore.co.uk>
References: <1432951079-24456-1-git-send-email-developer@it-offshore.co.uk>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Sat, 30 May 2015 01:57:59 +0000
Stuart Cardall <developer@it-offshore.co.uk> wrote:

> http-sysguard: repo & release created
> upstream-fair: alternative repo with a release used
> 
> http-sysguard updated to use the latest features in tengine 2.1.0:
> http://tengine.taobao.org/document/http_sysguard.html

I have applied this. Thanks!

But to be honest, I am not to happy with that we need an nginx build
for every single module. If nginx gets an update we need to update *
number-of-modules. If we want an improvement in the nginx init.d
script, then we need to update * number-of-modules.

If there is a security issue, then we will have to patch *
number-of-modules.

This is a maintenance nightmare.

Why can not modules be implemented as dynamic libs (like tengine does).


-nc


---
Unsubscribe:  alpine-aports+unsubscribe@lists.alpinelinux.org
Help:         alpine-aports+help@lists.alpinelinux.org
---