> > > 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 majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
