On Thu, 3 May 2001 12:59:21 -0400,
"Eric S. Raymond" <[EMAIL PROTECTED]> wrote:
>Keith Owens <[EMAIL PROTECTED]>:
>> (3) For failing constraints, freeze the guard variables, change
>> the dependent variable to satisfy the constraint then
>> freeze it.
>
>There's th
> You want brutality and heuristics? I'll give you brutality and heuristics...
> I could just treat a config as a sequence of assignments, as though
> the user had typed them in sequence, rejecting any later ones that
> throw constraint violations. That way we can avoid ever accepting or
> havin
Alan Cox <[EMAIL PROTECTED]>:
> If you get a conflict, turn the second feature in config file order off/on
> as appropriate then tell the user you did it. Then continue to verify.
> Actually I think the problem is different. You are trying to solve a
> mathematical graph theory problem elegantl
> (For those of you haven't caught up with this, *missing symbols do not
> make a configuration invalid*. Only inconsistencies between explicitly
> set symbols can do that.)
If they make it invalid the tools should fix it.
> > (ii) Start with a invalid config. CML2 makes best effort at correct
Keith Owens <[EMAIL PROTECTED]>:
> On Thu, 3 May 2001 03:47:55 -0400,
> "Eric S. Raymond" <[EMAIL PROTECTED]> wrote:
> >OK, so you want CML2's "make oldconfig" to do something more graceful than
> >simply say "Foo! You violated this constraint! Go fix it!"
>
> (i) Start with a valid config. CML
On Thu, 3 May 2001 03:47:55 -0400,
"Eric S. Raymond" <[EMAIL PROTECTED]> wrote:
>OK, so you want CML2's "make oldconfig" to do something more graceful than
>simply say "Foo! You violated this constraint! Go fix it!"
(i) Start with a valid config. CML2 will not allow any changes that
violate
Greg Banks <[EMAIL PROTECTED]>:
> There is a natural order for presenting variables to the
> user, and that's the menu tree order. At least in the Linux
> kernel CML2 corpus the menus are roughly organised from most
> general to most specific options, so options appearing earlier
> in the tree
Eric S. Raymond wrote:
>
I agree with the main thrust of your argument, but
> It would be hard to know how to order your candidates to present
> them to the user in a natural sequence -- and the problem of deciding
> which variable to present for mutation by the user next, if you choose
> tha
8 matches
Mail list logo
