Re: Quick and dirty miniconfig howto, with feature suggestions.

[Rob Landley <rob@landley.net>]

On Saturday 19 November 2005 21:08, Roman Zippel wrote:
> Hi,
>
> On Thu, 17 Nov 2005, Rob Landley wrote:
> > 1) Add a "make miniconfig" which works like allnoconfig but A) takes
> > mini.config as its' default name, B) redirects stdout to /dev/null to
> > make it easier to spot typoed symbols, C) aborts (exits with an error,
> > does not write new .config) if mini.config isn't found or if it contains
> > an unrecognized symbol.
>
> I think I better make allnoconfig silent (unless with V=1 or something),
> which makes it your miniconfig already almost like allnoconfig.

That would be an improvement, but I think from a user interface perspective 
it's slightly confusing to overload allnoconfig.  (It's not a big issue 
either way, though.)

The output redirecton could actually be done trivially in the makefile without 
touching the config code, and the other changes I proposed are fairly small.    
I have a todo item to whip up a "make miniconfig" patch that adds a new 
target with all three of the small behavior changes.  I can submit that for 
consideration later this evening...

> I'm not quite sure about aborting there are other error possibilities
> (e.g. new dependencies), so you never quite can trust the error value
> anyway.

In theory, something based on allnoconfig shouldn't care about the previous 
state of the .config file, so how is a dependency "new"?  (Could you clarify 
what you mean?)

If the Kconfig tree has conflicting symbols in it (dependencies on something 
it can't find), then yeah it would exit with an error in that case.  But I'm 
not sure that's a down side, that's detecting a bug.

My use case is that I'm trying to run the build within a script, and if 
something goes wrong I want the build to abort then rather than have to 
backtrack later.  And when I'm testing it out from the command line, several 
times I've typoed "KCONFIG_ALLCONFIG=../path/to/miniconfig", and right now it 
happily does an allnoconfig that I have to examine to see if it's correct.  
For allnoconfig, there not being an allno.conf file is fine, but for 
miniconfig the action would be meaningless if the mini.conf isn't found, so 
it should error.

My take, anyway.  I'll come up with a patch...

Rob