linux-kernel - Re: [v4l-dvb-maintainer] [PATCH 35/36] Use menuconfig objects II

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070503204942.GB18539@uranus.ravnborg.org>
Date:	Thu, 3 May 2007 22:49:42 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Trent Piepho <xyzzy@...akeasy.org>,
	Roman Zippel <zippel@...ux-m68k.org>
Cc:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	v4l-dvb maintainer list <v4l-dvb-maintainer@...uxtv.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [v4l-dvb-maintainer] [PATCH 35/36] Use menuconfig objects II - DVB

Please include Roman Zippel when you propose kconfig changes.

	Sam
> 
> Jan, have you looked at the effect these changes have when using xconfig, and
> not just menuconfig?
> 
> While your changes make menuconfig better, they have nearly opposite effect on
> xconfig.
> 
> xconfig has the menu tree display in the left panel, where one can see the
> overall layout of the menu tree and jump directly to any menu (even one
> multiple levels deep).  All the menuconfigs that used to be menus don't show
> up here anymore.
> 
> To turn a menuconfig off, you must go to the top level menu containing the
> menuconfig you want (and you must know which one that is!).  Then you have to
> drill down through each menu level one by one, by finding that menu in the top
> panel (which also has all the config options listed) and clicking on it to get
> to the next one.  When you get to the menuconfig you want, you must enter it
> and then you finally get the box to turn that menuconfig off.
> 
> It looks like your changes are going in, so I suppose the solution is to
> improve the way xconfig handles "menuconfig".
> 
> I wonder, would it be possible to change the kconfig language so that:
> menuconfig XXXX
> 	boolean "name of menu"
> 
> Did the same thing as:
> config XXXX
> 	boolean "name of menu"
> menu "name of menu"
> 	depends on XXXX
> 
> This way you could change this:
> 
> menuconfig XXXX
> if XXXX
> [....all the other options....]
> endif
> 
> Into this:
> 
> menuconfig XXXX
> [....all the other options....]
> endmenu
> 
> The reason is that a frontend would easily be able to understand the coupling
> between the "menuconfig XXXX" and the "if XXXX".  It will make it easier for
> the frontend to see that all the options are inside and controlled by the
> enclosing menuconfig.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/