From owner-freebsd-ports@FreeBSD.ORG Mon Oct 20 23:22:01 2014 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 0648742E for ; Mon, 20 Oct 2014 23:22:01 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 79C24B34 for ; Mon, 20 Oct 2014 23:21:59 +0000 (UTC) Received: from mandree.no-ip.org ([78.48.35.70]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MDymt-1Xuwji4AXv-00HRSl for ; Tue, 21 Oct 2014 01:21:58 +0200 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id C3AEE23CEF3 for ; Tue, 21 Oct 2014 01:21:56 +0200 (CEST) Message-ID: <54459914.8000203@gmx.de> Date: Tue, 21 Oct 2014 01:21:56 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: www/dansguardian revival? References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:/uMrMMONn1FuSTlWJ0R230jXvC4ZqntSNnJrWQ3Xb7cvfgC7abK Dvieh6szrhU5PncbK+pWjPBNHSGeMGIsYLfLsMFNnwaYsonqd39YZCd/xhCToZw8QLHs4Xg aMn+7sF5dNv+HtSaReB4fBe5xNVTY6Xcv6qUMLnEE3Om9G2pFzo0wsuy3vjac+/ziQWmmPP r61z8lJnl5LUO3vhXk8AA== X-UI-Out-Filterresults: notjunk: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: Mon, 20 Oct 2014 23:22:01 -0000 Am 21.10.2014 um 01:08 schrieb Nick Rogers: > Hello, > > I recently learned that the www/dansguardian port was deprecated due to its > dependency on the old www/squid port (squid 2.7). Is there any way this > port can be revived? I've been using it for years with great success > against newer versions of squid (3.3, 3.4). Usually I would just change the > RUN_DEPENDS to look for squid33 or squid34. The squid dependency could > arguably be removed entirely because all dansguardian does is proxy www > traffic to squid - it doesn't really matter what version it is and the > application itself does not require the squid port to run. Point being, the > port works just fine as is (was). In fact, it would work in its last-known > state correctly now that squid34 is simply www/squid. I realize the > maintainer has not updated the port in a while, but I've been using > dansguardian with FreeBSD for nearly the last decade and it is unfortunate > to see it removed as a port simply because the previous state of the squid > ports was undesirable. > > It would be great if this could be added back. Clearly I am not the only > one still using it. > > I've CC'd the current dansguardian source code maintainer and author in > hopes they can assist and find a new maintainer for the FreeBSD port. Nick, If you're comfortable with grabbing the last known version with Subversion, and a bit of Makefile tweaking, you can be the new maintainer as well. No formalities involved for application. We have the FreeBSD porter's handbook that describes the details. http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ Just submit the updated port through our Bugzilla at https://bugs.freebsd.org/bugzilla and stuff your mail address into the "MAINTAINER=" line, and a committer will take care of reviving it. Cheers, Matthias