[oe] RFC: Inclusion of bootloader utilities in task-base
k.kooi at student.utwente.nl
Sun Dec 2 09:19:15 CET 2007
-----BEGIN PGP SIGNED MESSAGE-----
Rod Whitby schreef:
> 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
> 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.
I'm not familiar with the finer points of bootloaders, so I'm not really
qualified to respond to this, but if the utils are _critical_, they
should be RDEPENDS in task-boot, not task base.
> 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
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
koen at dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi at student.utwente.nl instead.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
-----END PGP SIGNATURE-----
More information about the Openembedded-devel