Warner Losh wrote:
> In message <[EMAIL PROTECTED]> John Baldwin writes:
> : 2) It hides the output from config(8).  config(8) prints out all sorts of
> : useful warnings when options are deprecated, etc., but buildkernel hides th
> : from the user.  The problem is that config(8) is by design an interactive t
> : which buildkernel fails to take into account.  The hack now is to have
> : config(8) treat warnings as errors instead. :-/
> config is not an interactive tool, any more than the compiler is an
> interactive tool.

Config is *loaded* with places where it does not return an error code
if something is wrong.  This is a recipe for disaster by automating it so
that people can do a 'make buildkernel' and switch to a different vty/window
and never see that there were 30000 parse errors in their kernel config file.

That is the fundamental problem.  I've started converting the notices in
config(8) to fatal errors that I hope buildkernel will pick up, but it is
IMHO still wrong, especially for -current that is changing on a daily basis.

-stable is a different story, but this is outright deadly for -current.

"All of this is for nothing if we don't go to the stars" - JMS/B5

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to