From owner-freebsd-current Mon Jun 7 12:34: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (unknown [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 63C3814C57 for ; Mon, 7 Jun 1999 12:33:29 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA20840; Mon, 7 Jun 1999 13:33:24 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA08776; Mon, 7 Jun 1999 13:33:23 -0600 Date: Mon, 7 Jun 1999 13:33:23 -0600 Message-Id: <199906071933.NAA08776@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chuck Robey Cc: Nate Williams , David Scheidt , freebsd-current@FreeBSD.ORG Subject: Re: bsd.lib.mk "@"'s In-Reply-To: References: <199906071921.NAA08649@mt.sri.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Who's worried about signal to noise there? > > > > I am, if I'm the developer trying to debug a user's problem. Wading > > through 1-2M of logfiles to find a problem is much less likely than me > > wading through 100-200K of logfiles. > > Wait a second. bsd.lib.mk is for our buildworld, right? It's for building source files in the source tree. Buildworld is *ONE* time that we build sources, but certainly not the only time it's used. > If you're hijacking it for customers, that's fine, but it's for > buildworld for FreeBSD, not for everyone's customers. What *are* you talking about? 'buildworld' is a FreeBSD'izm, and bsd.lib.mk predates it. bsd.lib.mk is part of all of the *BSD's, so equating /usr/share/mk/*.mk as only needed for 'world' building is an incorrect assumption. I have no 'FreeBSD' customers, so any assumptions you want to make about me using FreeBSD as a platform other than as a personal development platform are incorrect. > When you get to the problem, you want to know why it broke. And 99/100 (heck, I'd go 99.999999/100) the problem will not require the output of the '@' commands, so adding their output to the logfile only serves to create un-necessary noise and potentially confuse the users. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message