Ensure that this section correctly and accurately describes how Poky and
OE relate to eachother currently.
Signed-off-by: Paul Eggleton <paul.eggle...@linux.intel.com>
---
documentation/poky-ref-manual/faq.xml | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/documentation/poky-ref-manual/faq.xml
b/documentation/poky-ref-manual/faq.xml
index ad8fc7a..ab36f42 100644
--- a/documentation/poky-ref-manual/faq.xml
+++ b/documentation/poky-ref-manual/faq.xml
@@ -13,14 +13,14 @@
</question>
<answer>
<para>
- 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
<ulink
- url='&OE_HOME_URL;'>OpenEmbedded</ulink>.
- 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 upon
+ <ulink url='&YOCTO_DOCS_DEV_URL;#oe-core'>OE-Core</ulink>
+ and BitBake and 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, benefiting both projects immediately.
For a fuller description of the term "Poky", see the
<ulink url='&YOCTO_DOCS_DEV_URL;#poky'>poky</ulink> term in
the Yocto Project
Development Manual.
--
1.7.9.5
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
