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