From owner-freebsd-ports@FreeBSD.ORG Thu Feb 19 01:50:45 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D13DE25 for ; Thu, 19 Feb 2015 01:50:45 +0000 (UTC) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB8943C5 for ; Thu, 19 Feb 2015 01:50:44 +0000 (UTC) Received: by lbdu14 with SMTP id u14so4890202lbd.1 for ; Wed, 18 Feb 2015 17:50:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=3N8BcpUGzklDfXOznZyk3FbqEavG3xn6Hr7FNZxBTcw=; b=GvZjlcGczWy07BjkmbBJcS+wovQAQxZ0ckLDKCObQ+qOTLq3oT9PjUtXkSkVPEyfAv 95xuO4xLNGoJZ6Y5+Arqlb/o2S9wpiTqLPTYV+bxziaClC2wgaqYsQiaSTea8h2vsort q0INMdBElyE/z5bj+oCWNk2aVNsvfwVZ8uBU0CyV0/UDfKkVYLdggwEuM2uUzykuCvFQ 0ziXttx715HkDQuW7wTEc4z83k82qh+ObZHb8r5e68D6n9mnszWveqUUo9sTq0sWROy0 ix13KruD2fd8A1W+KGlE1qvp6m/g4pkzJs4NXpbOnMUtFPCcbEfhNo3o/FKcplkz4hCv wOmg== MIME-Version: 1.0 X-Received: by 10.112.65.196 with SMTP id z4mr2013835lbs.28.1424310642201; Wed, 18 Feb 2015 17:50:42 -0800 (PST) Received: by 10.25.90.131 with HTTP; Wed, 18 Feb 2015 17:50:42 -0800 (PST) Date: Wed, 18 Feb 2015 17:50:42 -0800 Message-ID: Subject: squid 3.5 plans From: Nick Rogers To: "freebsd-ports@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Thu, 19 Feb 2015 01:50:45 -0000 It seems that squid 3.5 is becoming the latest recommended production quality version. Squid 3.4.12 and 3.5.2 were just released today. What is everyones thought (or the maintainers plan) on moving the www/squid port from 3.4 to 3.5? It looks like the www/squid33 port has been kept around past its ideal expiration date because of an issue with ntlm_auth affecting squid 3.4. This bug has been fixed in the latest 3.4 and 3.5 release. http://bugs.squid-cache.org/show_bug.cgi?id=3997 So is the idea to now move the www/squid port to 3.5, or create yet another squid port of www/squid35 because we want to keep 3.4 as the "stable" version for a while. I am just wondering because I would like to move my production environment from squid 3.4 to 3.5, and am happy to contribute patches to the ports tree, but am not sure what the plans are. Thanks. -Nick