dev-manual: Changed "Tasks" term into "Package Groups" term.
Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: faa7206b2f67a26c1366fe997cd092aed7e9f85e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
17ac9ee194
commit
85e4bb6670
|
@ -430,7 +430,7 @@
|
|||
<note>
|
||||
The recommended method for setting up the Yocto Project
|
||||
<link linkend='source-directory'>Source Directory</link> and the
|
||||
files for supported BSPs (eg., <filename>meta-intel</filename>) is to
|
||||
files for supported BSPs (e.g., <filename>meta-intel</filename>) is to
|
||||
use <link linkend='git'>Git</link> to create a local copy of the
|
||||
upstream repositories.
|
||||
</note>
|
||||
|
@ -656,6 +656,17 @@
|
|||
<ulink url='&YOCTO_DOCS_REF_URL;#var-PV'><filename>PV</filename></ulink>, and
|
||||
<ulink url='&YOCTO_DOCS_REF_URL;#var-PE'><filename>PE</filename></ulink>).
|
||||
</para></listitem>
|
||||
<listitem><para><emphasis>Package Groups:</emphasis>
|
||||
Arbitrary groups of software Recipes.
|
||||
You use package groups to hold recipes that, when built,
|
||||
usually accomplish a single task.
|
||||
For example, a package group could contain the recipes for a
|
||||
company’s proprietary or value-add software.
|
||||
Or, the package group could contain the recipes that enable
|
||||
graphics.
|
||||
A package group is really just another recipe.
|
||||
Because package group files are recipes, they end with the
|
||||
<filename>.bb</filename> filename extension.</para></listitem>
|
||||
<listitem><para id='poky'><emphasis>Poky:</emphasis> The term "poky" can mean several things.
|
||||
In its most general sense, it is an open-source project that was initially developed
|
||||
by OpenedHand. With OpenedHand, poky was developed off of the existing OpenEmbedded
|
||||
|
@ -732,13 +743,6 @@
|
|||
repositories, branches, and tags, see the
|
||||
"<link linkend='repositories-tags-and-branches'>Repositories, Tags, and Branches</link>"
|
||||
section.</para></listitem>
|
||||
<listitem><para><emphasis>Tasks:</emphasis> Arbitrary groups of software Recipes.
|
||||
You use tasks to hold recipes that, when built, usually accomplish a single task.
|
||||
For example, a task could contain the recipes for a company’s proprietary or value-add software.
|
||||
Or, the task could contain the recipes that enable graphics.
|
||||
A task is really just another recipe.
|
||||
Because task files are recipes, they end with the <filename>.bb</filename> filename
|
||||
extension.</para></listitem>
|
||||
<listitem><para><emphasis>Upstream:</emphasis> A reference to source code or repositories
|
||||
that are not local to the development system but located in a master area that is controlled
|
||||
by the maintainer of the source code.
|
||||
|
|
Loading…
Reference in New Issue