summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml20
1 files changed, 12 insertions, 8 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index c335fccb21..6c0988089e 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -430,7 +430,7 @@
430 <note> 430 <note>
431 The recommended method for setting up the Yocto Project 431 The recommended method for setting up the Yocto Project
432 <link linkend='source-directory'>Source Directory</link> and the 432 <link linkend='source-directory'>Source Directory</link> and the
433 files for supported BSPs (eg., <filename>meta-intel</filename>) is to 433 files for supported BSPs (e.g., <filename>meta-intel</filename>) is to
434 use <link linkend='git'>Git</link> to create a local copy of the 434 use <link linkend='git'>Git</link> to create a local copy of the
435 upstream repositories. 435 upstream repositories.
436 </note> 436 </note>
@@ -656,6 +656,17 @@
656 <ulink url='&YOCTO_DOCS_REF_URL;#var-PV'><filename>PV</filename></ulink>, and 656 <ulink url='&YOCTO_DOCS_REF_URL;#var-PV'><filename>PV</filename></ulink>, and
657 <ulink url='&YOCTO_DOCS_REF_URL;#var-PE'><filename>PE</filename></ulink>). 657 <ulink url='&YOCTO_DOCS_REF_URL;#var-PE'><filename>PE</filename></ulink>).
658 </para></listitem> 658 </para></listitem>
659 <listitem><para><emphasis>Package Groups:</emphasis>
660 Arbitrary groups of software Recipes.
661 You use package groups to hold recipes that, when built,
662 usually accomplish a single task.
663 For example, a package group could contain the recipes for a
664 company’s proprietary or value-add software.
665 Or, the package group could contain the recipes that enable
666 graphics.
667 A package group is really just another recipe.
668 Because package group files are recipes, they end with the
669 <filename>.bb</filename> filename extension.</para></listitem>
659 <listitem><para id='poky'><emphasis>Poky:</emphasis> The term "poky" can mean several things. 670 <listitem><para id='poky'><emphasis>Poky:</emphasis> The term "poky" can mean several things.
660 In its most general sense, it is an open-source project that was initially developed 671 In its most general sense, it is an open-source project that was initially developed
661 by OpenedHand. With OpenedHand, poky was developed off of the existing OpenEmbedded 672 by OpenedHand. With OpenedHand, poky was developed off of the existing OpenEmbedded
@@ -732,13 +743,6 @@
732 repositories, branches, and tags, see the 743 repositories, branches, and tags, see the
733 "<link linkend='repositories-tags-and-branches'>Repositories, Tags, and Branches</link>" 744 "<link linkend='repositories-tags-and-branches'>Repositories, Tags, and Branches</link>"
734 section.</para></listitem> 745 section.</para></listitem>
735 <listitem><para><emphasis>Tasks:</emphasis> Arbitrary groups of software Recipes.
736 You use tasks to hold recipes that, when built, usually accomplish a single task.
737 For example, a task could contain the recipes for a company’s proprietary or value-add software.
738 Or, the task could contain the recipes that enable graphics.
739 A task is really just another recipe.
740 Because task files are recipes, they end with the <filename>.bb</filename> filename
741 extension.</para></listitem>
742 <listitem><para><emphasis>Upstream:</emphasis> A reference to source code or repositories 746 <listitem><para><emphasis>Upstream:</emphasis> A reference to source code or repositories
743 that are not local to the development system but located in a master area that is controlled 747 that are not local to the development system but located in a master area that is controlled
744 by the maintainer of the source code. 748 by the maintainer of the source code.