public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: John Stoffel <stoffel@casc.com>
Cc: CML2 <linux-kernel@vger.kernel.org>, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2 1.3.1, aka "I stick my neck out a mile..."
Date: Mon, 30 Apr 2001 13:39:32 -0400	[thread overview]
Message-ID: <20010430133932.B28849@thyrsus.com> (raw)
In-Reply-To: <20010427193501.A9805@thyrsus.com> <15084.12152.956561.490805@gargle.gargle.HOWL> <20010429183526.B32748@thyrsus.com> <15085.37569.205459.898540@gargle.gargle.HOWL>
In-Reply-To: <15085.37569.205459.898540@gargle.gargle.HOWL>; from stoffel@casc.com on Mon, Apr 30, 2001 at 12:28:49PM -0400

John Stoffel <stoffel@casc.com>:
> It should then highlight *all* of the potential problem config
> setting(s) and let the user deal.  But they should never be forced to
> hand edit their config file because a dependency is broken somewhere.
> CML2 should enforce the *writing* of compliant files, but should deal
> gracefully with non-compliant ones.  Within reason of course.  

The "within reason" is the problem.  It's very easy to construct
simple cases of invalid configs that blow the number of `tainted'
symbols up much larger than the number of violated constraints.  An
interface of the kind you suggest would deluge the user with possible
things to be corrected without actually revealing the nature of the
problem.

Besides, right now the configurator has a simple invariant.  It will
only accept consistent configurations and it will only write
consistent configurations -- in fact, your configuration is guaranteed
correct after ever attempt to change a symbol with the configurator
itself.  I'm very, very reluctant to do anything that will go near
breaking that invariant.

I believe the the right fix is to go through the one-time transition
necessary to be in a world where inconsistent configurations never get
written, rather than to be overly accomodating to yesterday's bugs.

> Eric> USB and SCSI are both enabled/disabled in the system buses menu.
> Eric> The apparent confusion
> 
> Then they should be pushed down a level to be under those buses.  They
> don't belong on the top level.

That doesn't work either.  See the "Good style in rulebase design"
section in the CML2 paper for discussion.  The last paragraph is
especially relevant.
 
> More correctly, *any* configuration setting on an upper level should
> not depend on a lower level setting.

Sorry, that's dreadfully bad advice and is not going to happen.  If I did
as you suggest, I'd be throwing out the ability to do consistency
checks and deduce side effects.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

"Those who make peaceful revolution impossible 
will make violent revolution inevitable."
	-- John F. Kennedy

  reply	other threads:[~2001-04-30 17:39 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27 23:35 CML2 1.3.1, aka "I stick my neck out a mile..." Eric S. Raymond
2001-04-29 15:12 ` John Stoffel
2001-04-29 22:35   ` Eric S. Raymond
2001-04-29 22:43     ` [kbuild-devel] " Eric S. Raymond
2001-04-30 16:28     ` John Stoffel
2001-04-30 17:39       ` Eric S. Raymond [this message]
2001-04-30 19:16         ` Peter Samuelson
2001-04-30 19:25           ` Eric S. Raymond
2001-05-01  9:23             ` Requirement of make oldconfig [was: Re: [kbuild-devel] Re: CML2 1.3.1, aka ...] Giacomo A. Catenazzi
2001-05-01 16:31               ` Eric S. Raymond
2001-05-01 21:35                 ` Olivier Galibert
2001-05-01 22:26                   ` Tom Rini
2001-05-02 13:32           ` Giacomo Catenazzi
2001-05-02 17:49             ` Eric S. Raymond
2001-05-02 20:12               ` John Stoffel
2001-05-03  7:04                 ` Hierarchy doesn't solve the problem Eric S. Raymond
2001-05-03  7:34                   ` Urban Widmark
2001-05-03  7:46                     ` Eric S. Raymond
2001-05-03 14:33                       ` Juan Quintela
2001-05-03 16:16                         ` Eric S. Raymond
2001-05-03 22:20                       ` Mike Castle
2001-05-03 12:32                 ` Requirement of make oldconfig [was: Re: [kbuild-devel] Re: CML2 1.3.1, aka ...] Horst von Brand
2001-05-03 12:47                   ` Alan Cox
2001-05-03 13:24                     ` Horst von Brand
2001-05-03 14:40                       ` Juan Quintela
2001-05-03 16:07                       ` Eric S. Raymond
2001-05-03 16:04                   ` Eric S. Raymond
2001-05-03 17:36                     ` Alan Cox
2001-04-30  1:36   ` CML2 1.3.1, aka "I stick my neck out a mile..." Anton Altaparmakov
2001-04-30  1:41     ` Eric S. Raymond
2001-04-30  2:13       ` [kbuild-devel] " John Cowan
2001-04-30  2:24       ` Alexander Viro
2001-04-30  5:41         ` David Emory Watson
2001-04-30  5:50           ` Alexander Viro
2001-04-30  6:12             ` David Emory Watson
2001-04-30  6:53               ` Eric S. Raymond
2001-04-30  7:11                 ` [OT] " Jeff Garzik
2001-04-30  7:17                 ` Alexander Viro
2001-04-30 14:25                   ` Kai Henningsen
2001-04-30 15:54                   ` [kbuild-devel] " Eric S. Raymond
2001-04-30 10:57                 ` John Cowan
2001-04-30 13:30               ` David Woodhouse
2001-04-30 13:29             ` David Woodhouse
2001-04-30  7:05         ` volodya
2001-04-30  7:23           ` Alexander Viro
2001-04-30  7:40             ` Eric S. Raymond
2001-04-30  9:09               ` [Moving rapidly offtopic] " Henning P. Schmiedehausen
2001-04-30 16:16               ` nick
2001-04-30 17:12                 ` [kbuild-devel] " Eric S. Raymond
2001-04-30 17:20                   ` [OT] " Jeff Garzik
2001-04-30 17:25                     ` Rik van Riel
2001-04-30 19:44                   ` [kbuild-devel] " Gerhard Mack
2001-04-30 19:47                     ` nick
2001-04-30  3:26       ` volodya
2001-04-30  7:52     ` Anton Altaparmakov
2001-04-30  8:03       ` Eric S. Raymond
2001-04-30 16:17         ` volodya
2001-04-30  8:13       ` Anton Altaparmakov
     [not found] ` <15084.12830.973535.153706@gargle.gargle.HOWL>
2001-04-29 22:41   ` Eric S. Raymond

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010430133932.B28849@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stoffel@casc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox