Re: [PATCH] make miniconfig (take 2)

[Kyle Moffett <mrmacman_g4@mac.com>]

On Nov 25, 2005, at 17:20:12, Rob Landley wrote:

> On Friday 25 November 2005 16:09, Pavel Machek wrote:
>
> > Ouch, I guess I killed my .config :-(. It seems that interrupted
> > miniconfig.sh leaves .config in close to empty state...
> That's why it insists you rename it in order to run it.
>
> I intend to fix that somewhat in a newer version of the sucker by  
> having the script intercept signals and restore .config on the way  
> out, but it can't be fully reliable (not against kill -9) because  
> kconfig overwrites .config and the script is repeatedly running  
> allnoconfig.  (I can probably bypass the makefile and feed it some  
> strange command line argument, but what Kconfig to run it on gets  
> us into architecture dependence issues the make file handles for  
> us...)
I got interested so I started writing a Perl-based replacement that  
actually reads the source config into program memory and writes  
copies out of that RAM each time.  I ran into a problem (although I  
can't reproduce it anymore) where the resultant configs had identical  
options but slightly altered whitespace or ordering, which naturally  
broke the diff method that miniconfig.sh used.

> > I'm not sure what I did wrong last time, it worked this time. My
> > miniconfig is 6K instead of 46K, good. Still its quite long. Thanks!
> You mentioned you set a lot of options. :)
>
> I agree scripts/miniconfig.sh is clumsy.  I'm thinking about  
> improvements (both to how it works and to the user interface), but  
> I need to catch up on some other stuff first...
I have a bit of time to tinker.  I'll send you my perl version once I  
get it working and test it out a bit.  It shouldn't be too hard to  
add the ability to use .config and rewrite that when exiting.
One other minor nit:  If you pass a config file from a previous  
version to miniconfig.sh, it will return the full config file because  
nothing makes it match the original.  Theoretically it should  
probably allnoconfig with the full config first and use that for the  
rest, before removing lines.
Cheers,
Kyle Moffett


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/