On 7 August 2010 11:19, Chris Larson <[email protected]> wrote: > > BOOTSTRAP_EXTRA_RDEPENDS is a remnant. We wouldn't want them controlling it > from there anyway. The fact that I INHERIT package_ipk doesn't mean I'm > constructing an ipk image, only that I'm *emitting* packages of that > format. IMAGE_PKGTYPE controls which rootfs_* bbclass will be used to > construct the image, but that doesn't control which package *manager* for > that type will be used, nor whether it should be installed at all > (ONLINE_PACKAGE_MANAGEMENT).
Thanks, that does clear up how things are intended to behave. However it doesn't reflect the reality of package_deb.bbclass and package_ipk.bbclass, which both add their package managers to the image unconditionally. i.e. using INHERIT="package_ipk" and ONLINE_PACKAGE_MANAGEMENT="none" will still get you an image with opkg installed. My intention here is to cut off some of opkg's tentacles in OE. I expect more pruning will be required. -Graham _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
