From owner-freebsd-ports@FreeBSD.ORG Thu Jan 15 18:48:50 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 10D40468 for ; Thu, 15 Jan 2015 18:48:50 +0000 (UTC) Received: from udns.ultimatedns.net (ultimatedns.net [209.180.214.225]) (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 C11ADDFF for ; Thu, 15 Jan 2015 18:48:49 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t0FIldmb032095; Thu, 15 Jan 2015 10:47:39 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: Nick Rogers In-Reply-To: References: <20141021093930.512251194d972a238e27e45a@mimar.rs> <727e7b743177b720d1d19bdf0e387166@ultimatedns.net>, From: "Chris H" Subject: Re: www/dansguardian revival? Date: Thu, 15 Jan 2015 10:47:39 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <69705840d3bd8cf82b8a0c4b4d72f30f@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: "freebsd-ports@freebsd.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: Thu, 15 Jan 2015 18:48:50 -0000 On Thu, 15 Jan 2015 08:42:21 -0800 Nick Rogers wrote > On Sun, Nov 2, 2014 at 1:00 PM, Chris H wrote: > > > On Fri, 31 Oct 2014 16:55:47 -0700 Nick Rogers wrote > > > > > On Tue, Oct 21, 2014 at 6:29 PM, Chris H wrote: > > > > > > > On Tue, 21 Oct 2014 09:39:30 +0200 Marko Cupać > > > > wrote > > > > > > > > > On Mon, 20 Oct 2014 17:47:19 -0700 > > > > > "Chris H" wrote: > > > > > > > > > > > Unless theirs any objection. I'll take it. I'll open a pr(1) > > > > > > with a shar(1) ready, in about an hour. > > > > > > > > > > > > --Chris > > > > > > > > > > Nice to hear that dansguardian will be back in ports. I also used it > > > > > for years in combination with www/squid33 without problem. I was > > > > > compiling it from ports, and the trick was to compile squid33 first, > > > > > and dansguardian only after, as dansguardian would only check > > existence > > > > > of /use/local/bin/squid, and if it was already there, no matter which > > > > > version, it would happily compile, install and work. > > > > > > > > Right. But there's ${STAGE} to deal with, as well. I may > > > > make sqid34 the DEPENDS (I'm still testing). > > > > I'm also working with the -devel version, and will likely > > > > convert it to the (un)devel version, as there is less user > > > > overhead involved -- RESTRICTED/COPYRIGHT/LICENSE/{...} > > > > > > > > Should be able to post a complete version, sometime > > > > tomorrow. > > > > > > > > > > Hey Chris. Any luck getting your new dansguardian port to work? I can't > > > find a PR for it. Just wondering if theres anything I can do to help test > > > or if it would be worth my while to just submit a PR with the last-known > > > www/dansguardian for the time being. Thanks. > > > > > > -Nick > > Sorry for the delay, and thank you for your generous offer, Nick. > > There were some issues with www/squid(34), and decided to wait > > to see if they would be addressed soonish. I see that there was > > a [partial] resolution just submitted. I'll see if they made it > > into the ports tree. If so, I'll see where things are with > > regard to their (e|a)ffect on www/dansguardian. If there's still > > issues, I'll take you up on your generous offer. :) > > > > Any luck with the squid issues and getting a new www/dansguardian going? > I'm still having success with www/squid and the old www/dansguardian, > albeit www/squid version needs to be bumped to the latest. Sorry for the delay, Nick. There's been a great deal of activity in the squid* department over the past couple months. I wanted to wait for the "dust to settle" before continuing; lest I be required to re-release every couple weeks to work with any new changes. On the up-side, things seem to have settled down. So I'll suck down a copy of HEAD, and renew my efforts to get this back in, over the next couple days. Again, sorry for the delay. Hope you understand. :) --Chris > > > > > > FWIW I run my dev box on 11 (CURRENT). > > > > Thanks, again. > > > > --Chris > > > > > > > > > > > > --Chris > > > > > > > > > > > > > -- > > > > > Marko Cupać > > > > > https://www.mimar.rs > > > > > _______________________________________________ > > > > > 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" > > > > > > > > > > > > _______________________________________________ > > > > 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" > > > > > > > _______________________________________________ > > > 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" > > > > > > _______________________________________________ > > 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" > > > _______________________________________________ > 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" --Chris ---