From: Stephen Wille Padnos <stephen.willepadnos@verizon.net>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: a really annoying feature of the config menu structure
Date: Tue, 18 Feb 2003 17:33:50 -0500 [thread overview]
Message-ID: <3E52B4CE.7040009@verizon.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0302181604310.23007-100000@dell>
[snip]
> as i see it, this can only get worse. the current
>erratic and disorganized structure of the config menus
>is proof of that.
>
> comments?
>
I think the problem with the "Multimedia" menu is that it's misnamed.
It should actually be the "tuners" menu - it's there for audio, digital
video, and video tuners. The same could be said of the networking menu,
and presumably others.
You can actually reorganize things simply by changing the structure of
the top-level Kconfig file. With the following patches, I reorganized
the multimedia options into the form that you are probably looking for.
(hopefully they won't be mangled by my mailer)
With not too much rewriting (many small changes, I think), the menus can
be organized much better.
Essentially, each subdirectory has a Kconfig file that does _not_
declare itself a standalone menu. This allows a parent to decide
whether or not to include it in another menu. The menu should only have
options that pertain to things in its' directory. ie, the Kconfig file
in drivers/net should not include "Networking" as an option - that is a
higher level decision (ie, it decides whether or not to include the
drivers/net config file).
Then, the Kconfig files from various subdirectories can be ordered in
whatever way makes sense from a user's point of view
--- drivers/media/Kconfig.orig 2003-02-18 17:15:46.000000000 -0500
+++ drivers/media/Kconfig.new 2003-02-18 17:25:27.000000000 -0500
@@ -2,8 +2,6 @@
# Multimedia device configuration
#
-menu "Multimedia devices"
-
config VIDEO_DEV
tristate "Video For Linux"
---help---
@@ -32,5 +30,4 @@
source "drivers/media/dvb/Kconfig"
-endmenu
--- arch/i386/Kconfig.orig 2003-02-18 17:17:49.000000000 -0500
+++ arch/i386/Kconfig 2003-02-18 17:18:32.000000000 -0500
@@ -1529,14 +1529,13 @@
source "drivers/char/Kconfig"
-#source drivers/misc/Config.in
-source "drivers/media/Kconfig"
-
source "fs/Kconfig"
source "drivers/video/Kconfig"
-menu "Sound"
+#source drivers/misc/Config.in
+menu "MultiMedia (tuners, sound, video"
+source "drivers/media/Kconfig"
config SOUND
tristate "Sound card support"
next prev parent reply other threads:[~2003-02-18 22:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 21:28 a really annoying feature of the config menu structure Robert P. J. Day
2003-02-18 22:33 ` Stephen Wille Padnos [this message]
2003-02-19 1:04 ` Robert P. J. Day
2003-02-19 1:24 ` Stephen Wille Padnos
2003-02-19 2:09 ` Robert P. J. Day
2003-02-19 1:56 ` Alan Cox
2003-02-19 1:31 ` Stephen Wille Padnos
2003-02-19 3:03 ` Alan Cox
2003-02-19 2:13 ` Robert P. J. Day
2003-02-19 9:49 ` Tomas Szepe
2003-02-19 13:19 ` Helge Hafting
2003-02-19 13:31 ` Robert P. J. Day
2003-02-19 14:35 ` John Bradford
2003-02-19 13:33 ` Robert P. J. Day
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=3E52B4CE.7040009@verizon.net \
--to=stephen.willepadnos@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.