Re: "menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-12 Thread Stefan Richter
Robert P. J. Day wrote: > but it should be obvious that, if you look at the Kconfig files, each > and every "select" directive has the potential to override a decision > you think you might have made elsewhere. In other words, the author of a Kconfig file should not assume he knows best how users

Re: "menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-12 Thread Robert P. J. Day
On Thu, 12 Apr 2007, Carlo Florendo wrote: > Robert P. J. Day wrote: > > (in short, if i, the builder, explicitly choose *not* to add a > > certain feature to my build, i think i have every right to expect that > > some other part of my configuration isn't quietly going to put some > > sub-choic

Re: "menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-12 Thread DervishD
Hi Carlo :) * Carlo Florendo <[EMAIL PROTECTED]> dixit: > Robert P. J. Day wrote: > > (in short, if i, the builder, explicitly choose *not* to add a > >certain feature to my build, i think i have every right to expect that > >some other part of my configuration isn't quietly going to put som

Re: "menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-11 Thread Carlo Florendo
Robert P. J. Day wrote: (in short, if i, the builder, explicitly choose *not* to add a certain feature to my build, i think i have every right to expect that some other part of my configuration isn't quietly going to put some sub-choice of that feature back in behind my back.) I agree with th

Re: "menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-11 Thread Robert P. J. Day
On Wed, 11 Apr 2007, Jan Engelhardt wrote: > > On Apr 11 2007 05:47, Robert P. J. Day wrote: > >> On Apr 11 2007 05:25, Robert P. J. Day wrote: > >> >On Wed, 11 Apr 2007, Jan Engelhardt wrote: > >> >> On Apr 11 2007 03:58, Robert P. J. Day wrote: > >> >> > >> >> A CONFIG_EMBEDDED bug. This should

Re: "menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-11 Thread Jan Engelhardt
On Apr 11 2007 05:47, Robert P. J. Day wrote: >> On Apr 11 2007 05:25, Robert P. J. Day wrote: >> >On Wed, 11 Apr 2007, Jan Engelhardt wrote: >> >> On Apr 11 2007 03:58, Robert P. J. Day wrote: >> >> >> >> A CONFIG_EMBEDDED bug. This should perhaps be changed. >> >> Or at best, deactivate the --->

Re: "menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-11 Thread Robert P. J. Day
On Wed, 11 Apr 2007, Jan Engelhardt wrote: > > On Apr 11 2007 05:25, Robert P. J. Day wrote: > >On Wed, 11 Apr 2007, Jan Engelhardt wrote: > >> On Apr 11 2007 03:58, Robert P. J. Day wrote: > >> > >> A CONFIG_EMBEDDED bug. This should perhaps be changed. > >> Or at best, deactivate the ---> part w

Re: "menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-11 Thread Jan Engelhardt
On Apr 11 2007 05:25, Robert P. J. Day wrote: >On Wed, 11 Apr 2007, Jan Engelhardt wrote: >> On Apr 11 2007 03:58, Robert P. J. Day wrote: >> >> A CONFIG_EMBEDDED bug. This should perhaps be changed. >> Or at best, deactivate the ---> part when it's N. > > i'm not sure what you mean by "bug". if

Re: "menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-11 Thread Robert P. J. Day
On Wed, 11 Apr 2007, Jan Engelhardt wrote: > > On Apr 11 2007 03:58, Robert P. J. Day wrote: > > > > General setup > >[ ] Configure standard kernel features (for small systems) ---> > > > >note how, even if you don't choose to configure features for small > >systems, if you go under that men

Re: "menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-11 Thread Jan Engelhardt
On Apr 11 2007 03:58, Robert P. J. Day wrote: > > General setup >[ ] Configure standard kernel features (for small systems) ---> > >note how, even if you don't choose to configure features for small >systems, if you go under that menu entry, you're still presented with >a couple config optio

"menu" versus "menuconfig" -- they're *both* a bad idea

2007-04-11 Thread Robert P. J. Day
i can still remember the days when *i* was pushing for the idea of using "menuconfig" instead of "menu" more in the config menus, but i've finally realized they're *both* badly designed for what jan is trying to do here. the best example of why "menuconfig" is a mess is in the menu entry for: