On Thu, 2011-05-19 at 12:21 +0100, Richard Purdie wrote: > On Thu, 2011-05-19 at 11:31 +0100, Phil Blundell wrote: > Agreed. I'd like to raise one other issue which is the number of > variables we need to control these things which are effectively binary > flags. I'm leaning towards having a small number of variables containing > flags which trigger certain behaviours. In this case the obvious choices > would be:
That's true, though one particular variable at hand is actually a trinary. The behaviour that we have historically had in OE, which seems to capture most of the significant use-cases, is: ONLINE_PACKAGE_MANAGEMENT="full" (or not set at all) means to install opkg or whatever and all its metadata, like oe-core does now ONLINE_PACKAGE_MANAGEMENT="none" means to not install opkg or its metadata on the target at all; ONLINE_PACKAGE_MANAGEMENT="add" means to install just enough package management infrastructure to allow new packages to be added after the fact, but not to allow packages that were shipped in the image to be manipulated. I think the main use case for this was language packs and the like. I'm not entirely sure that O_P_M="add" has ever actually worked properly (I don't use it myself) but it doesn't seem like an entirely worthless proposition. I agree that TARGET_READONLY_ROOTFS or whatever could be done just as well as some kind of FEATURE. p. _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
