Date: Mon, 02 Dec 2013 09:31:22 -0800 From: Darren Pilgrim <list_freebsd@bluerosetech.com> To: Ilya Bakulin <webmaster@kibab.com> Cc: freebsd-hackers@freebsd.org Subject: Re: unbound-control in FreeBSD-CURRENT and stable/10 Message-ID: <529CC3EA.4030202@bluerosetech.com> In-Reply-To: <7507eb85a259cbb96c232625bb883460@mail.bakulin.de> References: <20131129142143.GA29437@olymp.kibab.com> <20131129142729.GA29580@olymp.kibab.com> <5298EA83.30705@bluerosetech.com> <7507eb85a259cbb96c232625bb883460@mail.bakulin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/2/2013 4:56 AM, Ilya Bakulin wrote: > On 2013-11-29 20:26, Darren Pilgrim wrote: >> On 11/29/2013 6:27 AM, Ilya Bakulin wrote: >> >> There's really no bug to fix. The base has unbound in it, >> unbound-control is part of unbound. If you install unbound from >> ports, you should delete unbound from base. I haven't tried out 10.x >> yet, but you usually just set a knob like WITHOUT_UNBOUND in >> /etc/src.conf, then do: > > Why on earth I should rebuild the whole system just to get rid of > Unbound? Who said anything about running the buildworld target? Just do what my original email said: 1. Add the appropriate knob to /etc/src.conf 2. make delete-old delete-old-libs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?529CC3EA.4030202>