Hi Jeremy Have looked at this further and I really think this needs to be a separate utility, but one still written in python using bitbake's infrastructure (like bitbake-layers). The advantages of this approach:
1) Avoids reworking bitbake's initialisation and avoids possible re-execution. A separate utility can take advantage of a full parse and utilise all of the user's configuration. 2) Fetching/updating layers should be (able to be) a conscious action rather than something that happens implicitly as part of the build process I'm trying to put something together that does this at the moment, with a view to there being components that allow integration with the content tools you posted earlier. Will keep you posted. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
