From 70677171133f6698641d2dbb683ec469225ba570 Mon Sep 17 00:00:00 2001 From: Paul Eggleton Date: Tue, 2 Oct 2012 09:24:47 -0700 Subject: [PATCH] documentation: poky-ref-manual - Updates to faq entry Ensure that this section correctly and accurately describes how Poky and OE relate to eachother currently. The faq entry changed is "How does Poky differ from OpenEmbedded?" (From yocto-docs rev: ecc88ef12ec2faa48d05824e8b781a7d43e86127) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/poky-ref-manual/faq.xml | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml index c1a1390b36..943d22a7d8 100644 --- a/documentation/poky-ref-manual/faq.xml +++ b/documentation/poky-ref-manual/faq.xml @@ -13,14 +13,16 @@ - The term "Poky" is sometimes used to refer to the build system that the - Yocto Project uses. - The build system used in the Yocto project is referred to as the - OpenEmbedded build system because "Poky" was derived from OpenEmbedded. - Poky is a stable, smaller subset focused on the mobile environment. - Development in the Yocto Project using Poky is closely tied to OpenEmbedded with - features being merged regularly between the two for mutual benefit. + The term "Poky" refers to the specific reference build system that + the Yocto Project provides. + Poky is based on OE-Core + and BitBake. + Thus, the generic term used here for the build system is + the "OpenEmbedded build system." + Development in the Yocto Project using Poky is closely tied to OpenEmbedded, with + changes always being merged to OE-Core or BitBake first before being pulled back + into Poky. + This practice benefits both projects immediately. For a fuller description of the term "Poky", see the poky term in the Yocto Project Development Manual.