Precedence: list
MIME-Version: 1.0
In-Reply-To: <20180214213643.5bplV%steffen@sdaoden.eu>
References: <18a9b3a4-c34b-4727-28c6-0fb416b354a4@adelielinux.org> <20180214213643.5bplV%steffen@sdaoden.eu>
From: William Pitcock <nenolod@dereferenced.org>
Date: Wed, 14 Feb 2018 18:51:23 -0600
Message-ID: <CA+T2pCGKNEKQ3t2qGSy2ruNwuTK-811LzHf-RBfztq6=pHTjUQ@mail.gmail.com>
Subject: Re: [alpine-devel] Packages to consider moving from main/ to community/
To: "A. Wilcox" <awilfox@adelielinux.org>, 
	alpine-dev <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset="UTF-8"

Hello,

On Wed, Feb 14, 2018 at 3:36 PM, Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
> "A. Wilcox" <awilfox@adelielinux.org> wrote:
>  |We've made a list of packages currently in main/ that may be better
>  |suited to being in community/:
>  ...
>  |== HTTP servers ==
>  |
>  |Rationale: HTTP servers are notoriously terrible at security and having
>  |them in main means lots of maintenance work for Alpine to keep security
>  |fixes for them for years.
>  ...
>  |* lighttpd (+ acf-lighttpd)
>
> I understand only main/ is backward supported?
> But i really have to stand up for this one.
> Reported bugs end up in new releases occasionally, which then end
> in main by updating APKBUILD.  If i look at the commit log i see
> something back in July 2015, which surely was a pain.  Can a port
> be managed any cheaper than this one?

We suggested lighttpd for move to community because upstream is not
always fast on fixing security problems.

William


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---