Date: Thu, 15 Jan 2015 10:47:39 -0800 From: "Chris H" <bsd-lists@bsdforge.com> To: Nick Rogers <ncrogers@gmail.com> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: www/dansguardian revival? Message-ID: <69705840d3bd8cf82b8a0c4b4d72f30f@ultimatedns.net> In-Reply-To: <CAKOb=YbeEpOggMhXoYwvvG2nRT=554adoNmncS5hvmoZhCJY1A@mail.gmail.com> References: <CAKOb=YZyE%2BVnNNkQvEpw8bP=0FqSQtw56CjkoT4G9Dd43HitVw@mail.gmail.com> <b28a8d926970cbdb4d76fd23f8f161a4@ultimatedns.net> <20141021093930.512251194d972a238e27e45a@mimar.rs> <c7cd9d25374a8c0d9c9393e8a530b9d7@ultimatedns.net> <CAKOb=YY=WR4aNQRTPnDfaw_7p1XVQY0XQSiBH5O4Wb4hUNnt8A@mail.gmail.com> <727e7b743177b720d1d19bdf0e387166@ultimatedns.net>, <CAKOb=YbeEpOggMhXoYwvvG2nRT=554adoNmncS5hvmoZhCJY1A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 15 Jan 2015 08:42:21 -0800 Nick Rogers <ncrogers@gmail.com> wrote
> On Sun, Nov 2, 2014 at 1:00 PM, Chris H <bsd-lists@bsdforge.com> wrote:
>
> > On Fri, 31 Oct 2014 16:55:47 -0700 Nick Rogers <ncrogers@gmail.com> wrote
> >
> > > On Tue, Oct 21, 2014 at 6:29 PM, Chris H <bsd-lists@bsdforge.com> wrote:
> > >
> > > > On Tue, 21 Oct 2014 09:39:30 +0200 Marko Cupać <marko.cupac@mimar.rs>
> > > > wrote
> > > >
> > > > > On Mon, 20 Oct 2014 17:47:19 -0700
> > > > > "Chris H" <bsd-lists@bsdforge.com> 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
---
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69705840d3bd8cf82b8a0c4b4d72f30f>