From owner-freebsd-ports@freebsd.org Sat Aug 10 11:22:37 2019 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0870AB9F39 for ; Sat, 10 Aug 2019 11:22:37 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 465KTS36WRz4fWF for ; Sat, 10 Aug 2019 11:22:36 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from pi by home.opsec.eu with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hwPS5-000EfN-Uv; Sat, 10 Aug 2019 13:22:25 +0200 Date: Sat, 10 Aug 2019 13:22:25 +0200 From: Kurt Jaeger To: Martin =?iso-8859-1?Q?Waschb=FCsch?= Cc: freebsd-ports@freebsd.org Subject: Re: PHP version retirement Message-ID: <20190810112225.GE28929@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 465KTS36WRz4fWF X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.981,0]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; NEURAL_HAM_LONG(-1.00)[-0.999,0] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Aug 2019 11:22:37 -0000 Hi! [...] > Would it not be better to have, say, the last two versions before > current stable still in ports but with a huge disclaimer saying: > use at your own risk, etc.? > > What do y'all think? You make the case for something other systems call backports, basically, keeping stuff in working order in the tree. Backports in other systems need someone to take up stewardship. So, either a group steps forward and takes responsibility to keep them in working order in the generic tree, e.g. by - having a mailing list, e.g. backports@, - and changing the maintainer from ports@ to backports@ - and fixing PRs as they come up Or a group provides their own pkg repo that the normal pkg-user can reference to retrieve those older packages. Both approaches sound possible, but need a non-trivial amount of investment. -- pi@opsec.eu +49 171 3101372 One year to go !