From owner-freebsd-ports@FreeBSD.ORG Sun Jan 11 17:23:26 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 5923FFFC for ; Sun, 11 Jan 2015 17:23:26 +0000 (UTC) Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 11543A6C for ; Sun, 11 Jan 2015 17:23:26 +0000 (UTC) Received: by mail-qg0-f54.google.com with SMTP id l89so15081948qgf.13 for ; Sun, 11 Jan 2015 09:23:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cITK/wH/Uv9xtegPKx5i/sKz3ePECssf0JPWZclN/lQ=; b=tUUZaK3PJpYgFIohaDu22AP00JzLCcrK7cz16Mbnp+NovT3tCZfriBGEALINicZ/hy p4xLNvPnU0MpGWtDgxnGKlRS/8faaQ4kmRrqZdtFyaDp5muO/7N/GszpF8OOpDG68c8H FxR8OCahKsvrVxlDyE3XcETI5O8V9hPNgu8Ii8lpqMtcNuvjJvE7c1Aw8zaHNUSLZPaY FSnmamkMu6Blc72G5YK77WnUWce+QIiEFWhei00g3KPRKZhCR70dlcZSn3AIsO11pGzM PwAAekKpdyAjwkJ6Diw08Dyhou1FDgQSXU60AvQnV7oZAzccW4NaZG+5EiqxILaC4bsx 6xPg== MIME-Version: 1.0 X-Received: by 10.224.171.129 with SMTP id h1mr43818816qaz.74.1420997005226; Sun, 11 Jan 2015 09:23:25 -0800 (PST) Received: by 10.140.161.65 with HTTP; Sun, 11 Jan 2015 09:23:25 -0800 (PST) In-Reply-To: <201501111714.t0BHDwvA094684@fire.js.berklix.net> References: <201501111714.t0BHDwvA094684@fire.js.berklix.net> Date: Sun, 11 Jan 2015 17:23:25 +0000 Message-ID: Subject: Re: BIND REPLACE_BASE option From: Loganaden Velvindron To: "Julian H. Stacey" Content-Type: text/plain; charset=UTF-8 Cc: The BSD Dreamer , dougb@dougbarton.us, FreeBSD ports 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: Sun, 11 Jan 2015 17:23:26 -0000 On Sun, Jan 11, 2015 at 5:13 PM, Julian H. Stacey wrote: > Hi, Reference: >> From: The BSD Dreamer >> Date: Sat, 10 Jan 2015 21:25:11 -0600 > > The BSD Dreamer wrote: >> >> On 2015-01-09 07:42, Mathieu Arnold wrote: >> > +--On 8 janvier 2015 19:44:09 -0800 Doug Barton wrote: >> > | Can you please explain why this option was removed? It's been in the >> > | ports for over 13 years, and lots of users utilized it. >> > | >> > | I realize that BIND is no longer in the base in 10.x, but that would >> > | be a reason to make the option conditional, to continue to support the >> > | substantial user base that is still on 8.x and 9.x. >> > >> > I only removed it from bind99, it was never there in bind910. I removed it >> > because it was a poor design idea to begin with, and it was making the port >> > harder to maintain. Also, it was overwriting files in the base system, >> > which is a thing we do not want to do. >> > >> > All you need to do is add: >> > >> > named_program="/usr/local/sbin/named" >> > >> > to your rc.conf, like the message says when you install the port. >> > >> > It was a bit like the /usr/bin/perl symlink, it was time for it to go. >> >> But, it was a huge and sudden pain for it to suddenly disappear and break >> everything... >> >> I can only abandon FreeBSD as our DNS platform as fast as replacement systems >> appear. >> >> Why have we decided that we're going to cease FreeBSD for our DNS servers >> (after I had made such a strong case for FreeBSD?) Count the PORTREVISIONs >> to bind before 9.9.4 and after. Plus look at all the other annoying changes >> in those PORTREVISIONs without that things have been working fine for the >> rest of us before. >> >> I should've been home hours ago...if I haven't been stuck dealing with >> bizarre problems caused by updating a bunch of packages. >> >> Now I have update nagios-plugins, since base nslookup is gone. Does it end? > > > ( ... As another user/admin of named for years, I've also gnashed teeth > as FreeBSD re-arranged var & chroot & rndc paths yet again, per > version; Needing more version dependent additions to my multi > version wrapper shell. OK, perhaps inevitable, but ... ) > > The latest FreeBSD named annoyance, ripping named out of src/ (& > apparently abandoning the chroot too I've read ?!), caused me & Is there a rationale behind abandoing chroot() ? Is there a URL for that ? > presumably numerous other user admins to _Not_ upgrade FreeBSD boxes > until extra free time could be found to deal with FreeBSD gratuitously > consuming user time. > > Years back FreeBSD had too many broken ports, but at least then > broken code was still in ports/ even if not enough was marked with > Makefile BROKEN="cause", & often we needed numerous setenv DUDS > "onemore `printenv DUDS`" . > > Now FreeBSD ports is in some ways Worse, it regularly loses not > just broken but even working ports, for no Good reason (eg demime > & majordomo etc). > > Ports get regularly axed, so user admins know for each FreeBSD > upgrade we've first got to stumble over what ports commiters have > axed, then discover when axed, then recover back from svn to ports/, > then install marked BROKEN=, then develop a fix (if a fix is even > necessary!), then store the patch for automatic application by local > script, (in case FreeBSD fail to accept it ) then convince FreeBSD > that a butchered port thould be restored. > > FreeBSD ports axe men are damaging FreeBSD, they should just > assert BROKEN= on broken ports, & Never removing working ports/ ! > > Cheers, > Julian > -- > Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com > Indent previous with "> ". Interleave reply paragraphs like a play script. > Send plain text, not quoted-printable, HTML, base64, or multipart/alternative. > Practice French & support democracy ? Buy on 14 Jan http://www.charliehebdo.fr > _______________________________________________ > 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" -- This message is strictly personal and the opinions expressed do not represent those of my employers, either past or present.