Waldemar Brodkorb dixit: >On Mon, 18 Sep 2006 at 21:08 +0000, Thorsten Glaser wrote: >> [EMAIL PROTECTED] dixit: >> >> >+menu "Board specific packages" >> >+menu "Broadcom" >> >> Not two menus again, please. Why not "Broadcom specific packages"? > >Because it is designed to have more than Broadcom specific packages. >There will be soon Routerboard stuff or others. People should get >used to the structure before I branch FreeWRT 1.0.
That's exactly the reason. I propose to use, instead of your | menu "Board specific packages" | menu "Broadcom" | ... | endmenu | menu "Linksys" | ... | endmenu | ... | endmenu to use the following structure: | menu "Broadcom specific packages" | ... | endmenu | menu "Linksys specific packages" | ... | endmenu | ... >> Or make the menu items appear/disappear depending on the model >> selected? > >That would be nice, but I have no good idea how to do this. Ask a menuconfig expert. I am very annoyed by bugs in it anyway (Ctrl-U to erase the entire content of a larger input field like ssh key doesn't work, sometimes backspace doesn't work¹ (especially under GNU/Linux), don't even ask about window resizing and assorted segmentation faults). We need something different for the long term. Maybe someone can hack it so that submenus can also depend on configuration entries in the meanwhile? //mirabile -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them. If you don't believe in God, just consider God as Nature if you won't deny existence. -- Coywolf Qi Hunt _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
