From owner-freebsd-ports@FreeBSD.ORG Fri Feb 27 16:11:39 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F5A34E8 for ; Fri, 27 Feb 2015 16:11:39 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2605FF78 for ; Fri, 27 Feb 2015 16:11:38 +0000 (UTC) Received: from [192.168.1.23] (133.Red-83-58-4.dynamicIP.rima-tde.net [83.58.4.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id A4387438BC; Fri, 27 Feb 2015 10:11:30 -0600 (CST) Message-ID: <54F0972F.2060001@marino.st> Date: Fri, 27 Feb 2015 17:11:27 +0100 From: John Marino Reply-To: marino@freebsd.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org, timp87@gmail.com Subject: Re: squid 3.5 plans References: <1425045213133-5992417.post@n5.nabble.com> In-Reply-To: <1425045213133-5992417.post@n5.nabble.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2015 16:11:39 -0000 Hi Pavel, When we had 3 unmaintained squid ports, the idea was the get down to one, www/squid. The only reason www/squid33 is still in ports is because you requested an extension on it's removal due to the FreeBSD 10.1 RC issues. I personally don't want to see that contraction reversed. Upstream immediately EOL's the previous version, so we should too. when squid 3.5 is ready, it should go to www/squid. As far as we know, this is the intent of upstream The last thing I want to do is create new unmaintained ports (which is not even allowed anyway, all new ports must have a legit maintainer) So I would say, do extensive testing on 3.5 and verify it replaces 3.4 without issues, then we'll do that. It's still amazing to me how many people use squid yet nobody wants to maintain it. John