Re: [Ksummit-discuss] [TECH TOPIC] is Kconfig a bit hard sometimes?

[Laurent Pinchart <laurent.pinchart@ideasonboard.com>]

On Thursday 06 Jul 2017 17:40:29 Dan Carpenter wrote:
> People have mentioned "make oldconfig" but I've never had a lot of luck
> with that.  It always just prints "* Restart config..." and deletes my
> config.

I like oldconfig as it makes it easy to find about new options when upgrading 
the kernel. However, there's one thing that bothers me. When jumping by more 
than one kernel version, the number of options can be quite high, in which 
case I sometimes make mistakes answering questions. I'd love it if Kconfig 
allowed me to go back and correct mistakes, instead of having to note the 
option down and modify it manually afterwards.

> Also I hate menus.  It's such a pain if you want to enable a feature and
> you have to do a dungeon crawl through our menu system to try find it.
> 
> I wrote a script a couple years ago to create kernel configs.  I do a
> make defconfig, then I take a distro config and I do:
> 
>     for i in $(grep =m old_config) ; do
> 	./scripts/kconfig/kconfig set $i
>     done
> 
> This prints a lot of errors and the code is only half implemented but
> it's honestly the easiest way for me to get a bootable kernel these
> days.  If someone wanted to the could add a "./scripts/kconfig/kconfig
> file <name>" command that would read a line at a time and call
> `./scripts/kconfig/kconfig set $line` over and over.

-- 
Regards,

Laurent Pinchart