From owner-freebsd-ports@FreeBSD.ORG Fri Feb 27 13:53:34 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 0E65B63E for ; Fri, 27 Feb 2015 13:53:34 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1.freebsd.org (Postfix) with ESMTP id EBE13E2B for ; Fri, 27 Feb 2015 13:53:33 +0000 (UTC) Received: from msam.nabble.com (unknown [162.253.133.85]) by mwork.nabble.com (Postfix) with ESMTP id BC774153F9DF for ; Fri, 27 Feb 2015 05:53:35 -0800 (PST) Date: Fri, 27 Feb 2015 06:53:33 -0700 (MST) From: timp To: freebsd-ports@freebsd.org Message-ID: <1425045213133-5992417.post@n5.nabble.com> In-Reply-To: References: Subject: Re: squid 3.5 plans MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 13:53:34 -0000 There is no maintainer for squid ports, so I guess there is no plans. IMO www/squid33 should be removed, no reason to keep it in ports. www/squid should be moved to www/squid34 for some time (~3 or more months) www/squid should be upgraded to 3.5 branch. Meanwhile, I tried to create a port for 3.5. https://lists.freebsd.org/pipermail/freebsd-ports/2015-February/098178.html It's www/squid35, but it's not important for testing purpose. -- View this message in context: http://freebsd.1045724.n5.nabble.com/squid-3-5-plans-tp5990062p5992417.html Sent from the freebsd-ports mailing list archive at Nabble.com.