"Eric S. Raymond" wrote:
>
> Peter Samuelson <[EMAIL PROTECTED]>:
> > [esr]
> > > Besides, right now the configurator has a simple invariant. It will
> > > only accept consistent configurations
> >
> > So you are saying that the old 'vi .config; make oldconfig' trick is
> > officially unsupported? That's too bad, it was quite handy.
>
> Depends on how you define `unsupported'. Make oldconfig will tell you
> exactly and unambiguously what was wrong with the configuration. I think
> if you're hard-core enough to vi your config, you're hard-core enough to
> interpret and act on
>
> This configuration violates the following constraints:
> (X86 and SMP==y) implies RTC!=n
>
> without needing some wussy GUI holding your hand :-).
I think that a fundamental requirment is that 'make oldconfig' should
validate any configurations (also the wrong conf).
(If you correct your rules, our old .config can be invalid on a new
kernel, and we don't want regualary edit our .config).
My proposal is instaed of complain about configuration violatation,
you just wrote the possible correct configuration and prompt user to
select the correct configuration.
In the case you cite, e.g. oldconfig shoud prompt:
1) SMP=n
2) RTC=m
3) RTC=y
(assuming the ARCH is invariant).
To simplify your life you can require only tty (or ev. also menu mode)
for
there question. User normally use oldconfig in tty mode for simplicity
(there
are normally only few questions, thus is simple to have the question
already
in order, without to perse nearly empy menus).
giacomo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
