From owner-freebsd-ports@FreeBSD.ORG Tue Oct 21 00:46:36 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 AC2CB42A for ; Tue, 21 Oct 2014 00:46:36 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (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 758902AE for ; Tue, 21 Oct 2014 00:46:36 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id s9L0lJqY037641; Mon, 20 Oct 2014 17:47:19 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: "freebsd-ports@freebsd.org" , Nick Rogers In-Reply-To: References: From: "Chris H" Subject: Re: www/dansguardian revival? Date: Mon, 20 Oct 2014 17:47:19 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit Cc: maintainer@dansguardian.org, author@dansguardian.org 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: Tue, 21 Oct 2014 00:46:36 -0000 On Mon, 20 Oct 2014 16:08:43 -0700 Nick Rogers wrote > 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. > > Thanks. > > -Nick Unless theirs any objection. I'll take it. I'll open a pr(1) with a shar(1) ready, in about an hour. --Chris > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"