[oe] RFC: Inclusion of bootloader utilities in task-base

Rod Whitby rod at whitby.id.au
Sun Dec 2 01:47:19 UTC 2007


Some MACHINE configurations have FEATURES defined for 'uboot' and
'redboot'.  It looks like these are intended to identify the bootloader
used on that machine.

These turn on additions to RDEPENDS in task-base for some bootloader
utilities.

RFC #1: Is putting bootloader utilities in task-base a good idea in the
first place?  Surely it's something that you either need for first boot
(in which case it should be in the more primitive task-boot list), or
it's something you use rarely after first boot (in which case it
shouldn't be  wasting precious flash space in a task-base list but
should just be ipkg installed when needed).

RFC #2: Shouldn't these be RRECOMMENDS unless they are absolutely
critical, so that you can ipkg remove them if you don't want them.

RFC #3: I want to add an 'apex' FEATURE for the Apex bootloader, and
have that enable the 'apex-env' utility.  Any objections?  It would be
done in the way decided by RFC #2, and subject to an RFC #1 decision.

RFC #4: If a machine (like the ixp4xx) can use a number of different
bootloaders (redboot and apex in the case of the NSLU2), should they all
be listed as features in machine.conf?

-- Rod




More information about the Openembedded-devel mailing list