diff options
author | Paul Eggleton <paul.eggleton@linux.intel.com> | 2012-10-02 09:13:30 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-10-02 17:41:38 +0100 |
commit | dd7db5cf833894cee2af1bd53cdd6b5d55b6d11a (patch) | |
tree | 393c5051b82658e5e5601941d8fe8f4b7ef21e7e | |
parent | 56e07f651012ea7ff974333f89acf5b535159418 (diff) | |
download | poky-dd7db5cf833894cee2af1bd53cdd6b5d55b6d11a.tar.gz |
documentation: poky-ref-manual, dev-manual - added link to oe-core
* Explain that we test with a set of reference hardware rather than only
supporting hardware that we have (avoiding any implication that the
build system can't support other devices). These are in the
faq entry in the poky-ref-manual for the question of how we can
claim Poky / OpenEmbedded-Core is stable.
* Adjust the language so that it is OE-Core friendly, with a link to
the Development Manual for the definition of OE-Core.
(From yocto-docs rev: 5ff1604dd383b26e918c319fcbe46dd1589cebc5)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r-- | documentation/dev-manual/dev-manual-newbie.xml | 2 | ||||
-rw-r--r-- | documentation/poky-ref-manual/faq.xml | 14 |
2 files changed, 9 insertions, 7 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index 50ef6243ab..ccd29e246d 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml | |||
@@ -304,7 +304,7 @@ | |||
304 | <listitem><para id='metadata'><emphasis>Metadata:</emphasis> The files that BitBake parses when | 304 | <listitem><para id='metadata'><emphasis>Metadata:</emphasis> The files that BitBake parses when |
305 | building an image. | 305 | building an image. |
306 | Metadata includes recipes, classes, and configuration files.</para></listitem> | 306 | Metadata includes recipes, classes, and configuration files.</para></listitem> |
307 | <listitem><para><emphasis>OE-Core:</emphasis> A core set of metadata originating | 307 | <listitem><para id='oe-core'><emphasis>OE-Core:</emphasis> A core set of metadata originating |
308 | with OpenEmbedded (OE) that is shared between OE and the Yocto Project. | 308 | with OpenEmbedded (OE) that is shared between OE and the Yocto Project. |
309 | This metadata is found in the <filename>meta</filename> directory of the source | 309 | This metadata is found in the <filename>meta</filename> directory of the source |
310 | directory.</para></listitem> | 310 | directory.</para></listitem> |
diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml index 80b8501700..8054b11077 100644 --- a/documentation/poky-ref-manual/faq.xml +++ b/documentation/poky-ref-manual/faq.xml | |||
@@ -63,7 +63,7 @@ | |||
63 | <qandaentry> | 63 | <qandaentry> |
64 | <question> | 64 | <question> |
65 | <para> | 65 | <para> |
66 | How can you claim Poky is stable? | 66 | How can you claim Poky / OpenEmbedded-Core is stable? |
67 | </para> | 67 | </para> |
68 | </question> | 68 | </question> |
69 | <answer> | 69 | <answer> |
@@ -71,11 +71,13 @@ | |||
71 | There are three areas that help with stability; | 71 | There are three areas that help with stability; |
72 | <itemizedlist> | 72 | <itemizedlist> |
73 | <listitem><para>The Yocto Project team keeps | 73 | <listitem><para>The Yocto Project team keeps |
74 | <ulink url='&YOCTO_DOCS_DEV_URL;#poky'>Poky</ulink> small and focused. | 74 | <ulink url='&YOCTO_DOCS_DEV_URL;#oe-core'>OE-Core</ulink> small |
75 | It contains around 650 packages as compared to over 5000 for full | 75 | and focused, containing around 830 recipes as opposed to the thousands |
76 | OpenEmbedded.</para></listitem> | 76 | available in other OpenEmbedded community layers. |
77 | <listitem><para>The Yocto Project only supports hardware that the | 77 | Keeping it small makes it easy to test and maintain.</para></listitem> |
78 | team has access to for testing.</para></listitem> | 78 | <listitem><para>The Yocto Project team runs manual and automated tests |
79 | using a small, fixed set of reference hardware as well as emulated | ||
80 | targets.</para></listitem> | ||
79 | <listitem><para>The Yocto Project uses an an autobuilder, | 81 | <listitem><para>The Yocto Project uses an an autobuilder, |
80 | which provides continuous build and integration tests.</para></listitem> | 82 | which provides continuous build and integration tests.</para></listitem> |
81 | </itemizedlist> | 83 | </itemizedlist> |