[Bootmenu-devel] Bootmenu in extras(-devel)?

[Frantisek Dufka]

Carsten V. Munk wrote:
> Frantisek Dufka wrote:
>> Great. I had a quick look, it seems to work. Any reason why 
>> debian/compat and debian/control uses debhelper 5? I guess it is just 
>> the way it was generated. Gregale sdk uses version 4 so I tried to 
>> change it to 4 and it seems to work too. Maybe it can be downgraded? I 
>> only see
>> dh_gencontrol
>> dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
>> dh_md5sums
>> when building in Gregale but I see it in Diablo SDK (version 5) too.
>>
> Yeah, - it was made by dh_make and it probably defaults to 5, if it
> works with 4 then sure
>> OK, no problem. I'd prefer to beat it into shape a bit before doing it 
>> (maybe version 1.4?) but I don't care too much if you insist :-)
>>
> I knew there was things that probably needed to be beat into shape so
> that was the whole point of this mail :)
>> Things I'd like to solve before doing that
>> - install_bootmenu vs refresh_bootmenu.d - they are modified copies of 
>> original initfs_flash, shared code should be moved somewhere else
> We can probably . in some shared methods

Maybe. And also we should take care of bigger diablo initfs which can be 
written directly so no reflashing needed. Also the sudo gainroot hack on 
the beginning could be replaced by adding those scripts to sudoers

> I kinda like the ITEM_ notation because it establishes a namespace and
> no matter what we do of changes in bootmenu / include variables, we
> won't accidentially overwrite anything

ok, maybe it is just NIH syndrom :-) and maybe we could prefix just 
ITEM_XX stuff with MENU_X_XX so for the rest there is a way to 
override/set some global settings too from *.item file when there is no 
ITEM_ on the beginning

>> - decide how to structure optional/extra features (dropbear, ...) so 
>> they can be included/omitted in the build (similar to 770 vs N8x0 
>> issue below)
>>
> Well I guess the challenge is - is the bootmenu package an automatic
> initfs flasher or a bootmenu installer (where you click an icon to
> install, and then select your options)?

Oh, good point. In that case debian build script should build several 
deb packages like (not sure about names)
bootmenu-initfs-flasher.deb or bootmenu-tools.deb
bootmenu-base.deb or bootmenu-bootmenu.deb
bootmenu-dropbear.deb
bootmenu-fbconsole.deb
..