On Sat, 6 Aug 2016 17:12:14 -0400
Brian Nash wrote:
> On Thu, Aug 04, 2016 at 02:36:06PM -0400, Steve Litt wrote:
> >The last two items on the preceding list are why deployment is so
> >problematic. On my system, each of my 237 submenus requires its
> >own .mnu (menu description) file. These are
What about the linux kconf menus?
(`make menuconfig`)
Once menuconfig is compiled, it is executed with a Kconfig file passed
as an argument. It loads the file (and included files) very quickly, and
the Kconfig files are _massive_.
After it loads the file(s), it parses them, then determines what
Hi Steve,
On 08/04/2016 11:32 PM, Steve Litt wrote:
The only ways I can think of to run single menus off the entire menu
system config is either:
1) Keep the entire config in a directory/file tree, or
Good :)
2) Keep the entire config in a quickly queryable database, hence the
questi
Hi all,
I asked a hypothetical question about dependencies, using a menu
program as an example. 3/4 of you were more interested in the nature of
the menu program than in its dependencies. Well, the good news is,
version 1 of this program, called UMENU, has existed since 1999 and in
its present for
