diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-03-09 13:40:39 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-03-23 14:24:43 +0000 |
commit | aa3a201629c7e40341f53d4be57b6e4223a845c8 (patch) | |
tree | 24e16d12dc67523d68b7c62eb2d9e8079bee8eb2 /documentation/dev-manual/dev-manual-newbie.xml | |
parent | e9c32b6a856aa4be4ec47b5e361a4441446204f2 (diff) | |
download | poky-aa3a201629c7e40341f53d4be57b6e4223a845c8.tar.gz |
documentation/dev-manual: Converted to use poky.ent
I converted the hard links to use the variables as established
in the file poky.ent.
Also, Cleaned up some bad text in the term "Yocto Project Files."
Looks like a cut-and-paste problem.
(From yocto-docs rev: e2e20bf4895d80dae73595e93132f37fb31121d1)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-newbie.xml')
-rw-r--r-- | documentation/dev-manual/dev-manual-newbie.xml | 129 |
1 files changed, 56 insertions, 73 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index cf6f700377..1da05e20df 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml | |||
@@ -1,5 +1,6 @@ | |||
1 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | 1 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" |
2 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> | 2 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" |
3 | [<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] > | ||
3 | 4 | ||
4 | <chapter id='dev-manual-newbie'> | 5 | <chapter id='dev-manual-newbie'> |
5 | 6 | ||
@@ -122,7 +123,7 @@ | |||
122 | 123 | ||
123 | <para> | 124 | <para> |
124 | The Yocto Project team maintains complete source repositories for all Yocto Project files | 125 | The Yocto Project team maintains complete source repositories for all Yocto Project files |
125 | at <ulink url='http://git.yoctoproject.org/cgit/cgit.cgi'></ulink>. | 126 | at <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi'></ulink>. |
126 | This web-based source code browser is organized into categories by function such as | 127 | This web-based source code browser is organized into categories by function such as |
127 | IDE Plugins, Matchbox, Poky, Yocto Linux Kernel, and so forth. | 128 | IDE Plugins, Matchbox, Poky, Yocto Linux Kernel, and so forth. |
128 | From the interface, you can click on any particular item in the "Name" column and | 129 | From the interface, you can click on any particular item in the "Name" column and |
@@ -143,7 +144,7 @@ | |||
143 | 144 | ||
144 | <para> | 145 | <para> |
145 | For any supported release of Yocto Project, you can go to the Yocto Project website’s | 146 | For any supported release of Yocto Project, you can go to the Yocto Project website’s |
146 | <ulink url='http://www.yoctoproject.org/download'>download page</ulink> and get a | 147 | <ulink url='&YOCTO_HOME_URL;/download'>download page</ulink> and get a |
147 | tarball of the release. | 148 | tarball of the release. |
148 | You can also go to this site to download any supported BSP tarballs. | 149 | You can also go to this site to download any supported BSP tarballs. |
149 | Unpacking the tarball gives you a hierarchical directory structure of Yocto Project | 150 | Unpacking the tarball gives you a hierarchical directory structure of Yocto Project |
@@ -158,14 +159,14 @@ | |||
158 | <para> | 159 | <para> |
159 | In summary, here is where you can get the Yocto Project files needed for development: | 160 | In summary, here is where you can get the Yocto Project files needed for development: |
160 | <itemizedlist> | 161 | <itemizedlist> |
161 | <listitem><para id='source-repositories'><emphasis><ulink url='http://git.yoctoproject.org/cgit/cgit.cgi'>Source Repositories:</ulink></emphasis> | 162 | <listitem><para id='source-repositories'><emphasis><ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi'>Source Repositories:</ulink></emphasis> |
162 | This area contains IDE Plugins, Matchbox, Poky, Poky Support, Tools, Yocto Linux Kernel, and Yocto | 163 | This area contains IDE Plugins, Matchbox, Poky, Poky Support, Tools, Yocto Linux Kernel, and Yocto |
163 | Metadata Layers. | 164 | Metadata Layers. |
164 | You can create Git repositories for each of these areas.</para> | 165 | You can create Git repositories for each of these areas.</para> |
165 | <para> | 166 | <para> |
166 | <imagedata fileref="figures/source-repos.png" align="center" width="6in" depth="4in" /> | 167 | <imagedata fileref="figures/source-repos.png" align="center" width="6in" depth="4in" /> |
167 | </para></listitem> | 168 | </para></listitem> |
168 | <listitem><para><anchor id='index-downloads' /><emphasis><ulink url='http://downloads.yoctoproject.org/releases/'>Index of /releases:</ulink></emphasis> | 169 | <listitem><para><anchor id='index-downloads' /><emphasis><ulink url='&YOCTO_DL_URL;/releases/'>Index of /releases:</ulink></emphasis> |
169 | This area contains index releases such as | 170 | This area contains index releases such as |
170 | the <trademark class='trade'>Eclipse</trademark> | 171 | the <trademark class='trade'>Eclipse</trademark> |
171 | Yocto Plug-in, miscellaneous support, Poky, pseudo, cross-development toolchains, | 172 | Yocto Plug-in, miscellaneous support, Poky, pseudo, cross-development toolchains, |
@@ -175,11 +176,11 @@ | |||
175 | <para> | 176 | <para> |
176 | <imagedata fileref="figures/index-downloads.png" align="center" width="6in" depth="4in" /> | 177 | <imagedata fileref="figures/index-downloads.png" align="center" width="6in" depth="4in" /> |
177 | </para></listitem> | 178 | </para></listitem> |
178 | <listitem><para><emphasis><ulink url='http://www.yoctoproject.org/download'>Yocto Project Download Page</ulink></emphasis> | 179 | <listitem><para><emphasis><ulink url='&YOCTO_HOME_URL;/download'>Yocto Project Download Page</ulink></emphasis> |
179 | This page on the Yocto Project website allows you to download any Yocto Project | 180 | This page on the Yocto Project website allows you to download any Yocto Project |
180 | release or Board Support Package (BSP) in tarball form. | 181 | release or Board Support Package (BSP) in tarball form. |
181 | The tarballs are similar to those found in the | 182 | The tarballs are similar to those found in the |
182 | <ulink url='http://downloads.yoctoproject.org/releases/'>Index of /releases:</ulink> area.</para> | 183 | <ulink url='&YOCTO_DL_URL;/releases/'>Index of /releases:</ulink> area.</para> |
183 | <para> | 184 | <para> |
184 | <imagedata fileref="figures/yp-download.png" align="center" width="6in" depth="4in" /> | 185 | <imagedata fileref="figures/yp-download.png" align="center" width="6in" depth="4in" /> |
185 | </para></listitem> | 186 | </para></listitem> |
@@ -239,12 +240,12 @@ | |||
239 | Images are the binary output that runs on specific hardware and for specific | 240 | Images are the binary output that runs on specific hardware and for specific |
240 | use cases. | 241 | use cases. |
241 | For a list of the supported image types that the Yocto Project provides, see the | 242 | For a list of the supported image types that the Yocto Project provides, see the |
242 | "<ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink>" | 243 | "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Reference: Images</ulink>" |
243 | appendix in The Yocto Project Reference Manual.</para></listitem> | 244 | appendix in The Yocto Project Reference Manual.</para></listitem> |
244 | <listitem><para id='layer'><emphasis>Layer:</emphasis> A collection of recipes representing the core, | 245 | <listitem><para id='layer'><emphasis>Layer:</emphasis> A collection of recipes representing the core, |
245 | a BSP, or an application stack. | 246 | a BSP, or an application stack. |
246 | For a discussion on BSP Layers, see the | 247 | For a discussion on BSP Layers, see the |
247 | "<ulink url='http://www.yoctoproject.org/docs/latest/bsp-guide/bsp-guide.html#bsp-layers'>BSP Layers</ulink>" | 248 | "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-layers'>BSP Layers</ulink>" |
248 | section in the Yocto Project Board Support Packages (BSP) Developer's Guide.</para></listitem> | 249 | section in the Yocto Project Board Support Packages (BSP) Developer's Guide.</para></listitem> |
249 | <listitem><para id='metadata'><emphasis>Metadata:</emphasis> The files that BitBake parses when | 250 | <listitem><para id='metadata'><emphasis>Metadata:</emphasis> The files that BitBake parses when |
250 | building an image. | 251 | building an image. |
@@ -283,44 +284,42 @@ | |||
283 | by cloning <filename>git://git.yoctoproject.org/poky</filename>. | 284 | by cloning <filename>git://git.yoctoproject.org/poky</filename>. |
284 | Sometimes the term "the Yocto Project Files structure" is used as well.</para> | 285 | Sometimes the term "the Yocto Project Files structure" is used as well.</para> |
285 | 286 | ||
286 | <para>The Yocto Project files contain BitBake, Documentation, metadata and | 287 | <para>The Yocto Project Files contain BitBake, Documentation, metadata and |
287 | other files that all support the development environment. | 288 | other files that all support the development environment. |
288 | Consequently, you must have the Yocto Project files in place on your development | 289 | Consequently, you must have the Yocto Project Files in place on your development |
289 | system in order to do any development using the Yocto Project.</para> | 290 | system in order to do any development using the Yocto Project.</para> |
290 | 291 | ||
291 | <para>The name of the top-level directory of the Yocto Project file structure | 292 | <para>The name of the top-level directory of the Yocto Project Files structure |
292 | is derived from the Yocto Project release tarball. | 293 | is derived from the Yocto Project release tarball. |
293 | For example, downloading and unpacking <filename>poky-edison-6.0.tar.bz2</filename> | 294 | For example, downloading and unpacking <filename>&YOCTO_POKY_TARBALL;</filename> |
294 | results in a Yocto Project file structure whose Yocto Project source directory is named | 295 | results in a Yocto Project file structure whose Yocto Project source directory is named |
295 | <filename>poky-edison-6.0</filename>. | 296 | <filename>&YOCTO_POKY;</filename>. |
296 | If you create a Git repository, then you can name the repository anything you like. | 297 | If you create a Git repository, then you can name the repository anything you like. |
297 | By default, your local Git repository is named <filename>poky</filename>.</para> | 298 | Throughout much of the documentation, the name of the Git repository is used as the |
299 | name for the local folder. | ||
300 | So, for example, cloning the <filename>poky</filename> Git repository results in a | ||
301 | local Git repository also named <filename>poky</filename>.</para> | ||
298 | 302 | ||
299 | <para>It is important to understand the differences between Yocto Project Files created | 303 | <para>It is important to understand the differences between Yocto Project Files created |
300 | by unpacking a release tarball as compared to cloning | 304 | by unpacking a release tarball as compared to cloning |
301 | <filename>git://git.yoctoproject.org/poky</filename>. | 305 | <filename>git://git.yoctoproject.org/poky</filename>. |
302 | When you unpack a tarball, you have an exact copy of the files based on the time of | 306 | When you unpack a tarball, you have an exact copy of the files based on the time of |
303 | release - a fixed release point. | 307 | release - a fixed release point. |
304 | Any changes you make to your local Yocto Project files are on top of the release. | 308 | Any changes you make to your local Yocto Project Files are on top of the release. |
305 | On the other hand, when you clone the Yocto Project Git repository, you have an | 309 | On the other hand, when you clone the Yocto Project Git repository, you have an |
306 | active development repository. | 310 | active development repository. |
307 | creates a build directory named <filename>YP-6.0</filename> | 311 | In this case, any local changes you make to the Yocto Project can be later applied |
308 | in your home directory within the directory <filename>mybuilds</filename>. | 312 | to active development branches of the upstream Yocto Project Git repository.</para> |
309 | If <filename>mybuilds</filename> does not exist it is created for you. In this case, any local changes you make to the Yocto Project can be later applied to active | 313 | |
310 | development branches of the upstream Yocto Project Git repository. | 314 | <para>Finally, if you want to track a set of local changes while starting from the same point |
311 | If you want to track a set of local changes while starting from the same point | ||
312 | as a release tarball, you can create a local Git branch that | 315 | as a release tarball, you can create a local Git branch that |
313 | reflects the exact copy of the files at the time of their release. | 316 | reflects the exact copy of the files at the time of their release. |
314 | You do this using Git tags that are part of the repository. | 317 | You do this using Git tags that are part of the repository.</para> |
315 | For more information on concepts, see the section | 318 | |
316 | "<link linkend='repositories-tags-and-branches'>Repositories, Tags, and Branches</link>". | 319 | <para>For more information on concepts around Git repositories, branches, and tags, |
317 | </para> | 320 | see the |
318 | 321 | "<link linkend='repositories-tags-and-branches'>Repositories, Tags, and Branches</link>" | |
319 | <para>You can find instruction on how to set up the Yocto Project files on your | 322 | section.</para></listitem> |
320 | host development system by reading | ||
321 | the | ||
322 | "<ulink url='http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#getting-setup'>Getting | ||
323 | Setup</ulink>" section.</para></listitem> | ||
324 | <listitem> | 323 | <listitem> |
325 | <para id='yocto-project-build-directory'><emphasis>Yocto Project Build Directory:</emphasis> | 324 | <para id='yocto-project-build-directory'><emphasis>Yocto Project Build Directory:</emphasis> |
326 | This term refers to the area used by the Yocto Project for builds. | 325 | This term refers to the area used by the Yocto Project for builds. |
@@ -341,17 +340,17 @@ | |||
341 | </literallayout></para></listitem> | 340 | </literallayout></para></listitem> |
342 | <listitem><para>Provide a directory path and specifically name the build | 341 | <listitem><para>Provide a directory path and specifically name the build |
343 | directory. | 342 | directory. |
344 | This next example creates a build directory named <filename>YP-6.0</filename> | 343 | This next example creates a build directory named <filename>YP-&POKYVERSION;</filename> |
345 | in your home directory within the directory <filename>mybuilds</filename>. | 344 | in your home directory within the directory <filename>mybuilds</filename>. |
346 | If <filename>mybuilds</filename> does not exist, the directory is created for you: | 345 | If <filename>mybuilds</filename> does not exist, the directory is created for you: |
347 | <literallayout class='monospaced'> | 346 | <literallayout class='monospaced'> |
348 | $ source poky-edison-6.0/oe-init-build-env $HOME/mybuilds/YP-6.0 | 347 | $ source &OE_INIT_PATH; $HOME/mybuilds/YP-&POKYVERSION; |
349 | </literallayout></para></listitem> | 348 | </literallayout></para></listitem> |
350 | <listitem><para>Provide an existing directory to use as the build directory. | 349 | <listitem><para>Provide an existing directory to use as the build directory. |
351 | This example uses the existing <filename>mybuilds</filename> directory | 350 | This example uses the existing <filename>mybuilds</filename> directory |
352 | as the build directory. | 351 | as the build directory. |
353 | <literallayout class='monospaced'> | 352 | <literallayout class='monospaced'> |
354 | $ source poky-edison-6.0/oe-init-build-env $HOME/mybuilds/ | 353 | $ source &OE_INIT_PATH; $HOME/mybuilds/ |
355 | </literallayout></para></listitem> | 354 | </literallayout></para></listitem> |
356 | </itemizedlist> | 355 | </itemizedlist> |
357 | </para></listitem> | 356 | </para></listitem> |
@@ -419,7 +418,7 @@ | |||
419 | 418 | ||
420 | <para> | 419 | <para> |
421 | You can find a list of the combined SPDX and OSI licenses that the Yocto Project uses | 420 | You can find a list of the combined SPDX and OSI licenses that the Yocto Project uses |
422 | <ulink url='http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/files/common-licenses'>here</ulink>. | 421 | <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/poky/tree/meta/files/common-licenses'>here</ulink>. |
423 | This wiki page discusses the license infrastructure used by the Yocto Project. | 422 | This wiki page discusses the license infrastructure used by the Yocto Project. |
424 | </para> | 423 | </para> |
425 | </section> | 424 | </section> |
@@ -449,7 +448,7 @@ | |||
449 | As mentioned earlier in section | 448 | As mentioned earlier in section |
450 | "<link linkend='yocto-project-repositories'>Yocto Project Source Repositories</link>", | 449 | "<link linkend='yocto-project-repositories'>Yocto Project Source Repositories</link>", |
451 | the Yocto Project maintains source repositories at | 450 | the Yocto Project maintains source repositories at |
452 | <ulink url='http://git.yoctoproject.org/cgit.cgi'></ulink>. | 451 | <ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink>. |
453 | If you look at this web-interface of the repositories, each item is a separate | 452 | If you look at this web-interface of the repositories, each item is a separate |
454 | Git repository. | 453 | Git repository. |
455 | </para> | 454 | </para> |
@@ -489,9 +488,9 @@ | |||
489 | <filename>edison</filename>, and <filename>master</filename> branches among | 488 | <filename>edison</filename>, and <filename>master</filename> branches among |
490 | others. | 489 | others. |
491 | You can see all the branches by going to | 490 | You can see all the branches by going to |
492 | <ulink url='http://git.yoctoproject.org/cgit.cgi/poky/'></ulink> and | 491 | <ulink url='&YOCTO_GIT_URL;/cgit.cgi/poky/'></ulink> and |
493 | clicking on the | 492 | clicking on the |
494 | <filename><ulink url='http://git.yoctoproject.org/cgit.cgi/poky/refs/heads'>[...]</ulink></filename> | 493 | <filename><ulink url='&YOCTO_GIT_URL;/cgit.cgi/poky/refs/heads'>[...]</ulink></filename> |
495 | link beneath the "Branch" heading. | 494 | link beneath the "Branch" heading. |
496 | </para> | 495 | </para> |
497 | 496 | ||
@@ -512,19 +511,19 @@ | |||
512 | branch in the repository. | 511 | branch in the repository. |
513 | To help illustrate, here is a set of commands that creates a local copy of the | 512 | To help illustrate, here is a set of commands that creates a local copy of the |
514 | <filename>poky</filename> Git repository and then creates and checks out a local | 513 | <filename>poky</filename> Git repository and then creates and checks out a local |
515 | Git branch that tracks the Yocto Project 1.1 Release (edison) development: | 514 | Git branch that tracks the Yocto Project &DISTRO; Release (&DISTRO_NAME;) development: |
516 | <literallayout class='monospaced'> | 515 | <literallayout class='monospaced'> |
517 | $ cd ~ | 516 | $ cd ~ |
518 | $ git clone git://git.yoctoproject.org/poky | 517 | $ git clone git://git.yoctoproject.org/poky |
519 | $ cd poky | 518 | $ cd poky |
520 | $ git checkout edison -b edison | 519 | $ git checkout &DISTRO_NAME; -b &DISTRO_NAME; |
521 | </literallayout> | 520 | </literallayout> |
522 | In this example, the name of the top-level directory of your local Yocto Project | 521 | In this example, the name of the top-level directory of your local Yocto Project |
523 | Files Git repository is <filename>poky</filename>. | 522 | Files Git repository is <filename>poky</filename>. |
524 | And, the name of the local working area (or local branch) you have created and checked | 523 | And, the name of the local working area (or local branch) you have created and checked |
525 | out is named <filename>edison</filename>. | 524 | out is named <filename>&DISTRO_NAME;</filename>. |
526 | The files in your repository now reflect the same files that are in the | 525 | The files in your repository now reflect the same files that are in the |
527 | <filename>edison</filename> development branch of the Yocto Project's | 526 | <filename>&DISTRO_NAME;</filename> development branch of the Yocto Project's |
528 | <filename>poky</filename> repository. | 527 | <filename>poky</filename> repository. |
529 | It is important to understand that when you create and checkout a | 528 | It is important to understand that when you create and checkout a |
530 | local working branch based on a branch name, | 529 | local working branch based on a branch name, |
@@ -532,8 +531,8 @@ | |||
532 | at the time you created your local branch, which could be | 531 | at the time you created your local branch, which could be |
533 | different than the files at the time of a similarly named release. | 532 | different than the files at the time of a similarly named release. |
534 | In other words, creating and checking out a local branch based on the | 533 | In other words, creating and checking out a local branch based on the |
535 | <filename>edison</filename> branch name is not the same as creating and | 534 | <filename>&DISTRO_NAME;</filename> branch name is not the same as creating and |
536 | checking out a local branch based on the <filename>edison-6.0</filename> | 535 | checking out a local branch based on the <filename>&DISTRO_NAME;-&DISTRO;</filename> |
537 | release. | 536 | release. |
538 | Keep reading to see how you create a local snapshot of a Yocto Project Release. | 537 | Keep reading to see how you create a local snapshot of a Yocto Project Release. |
539 | </para> | 538 | </para> |
@@ -543,15 +542,15 @@ | |||
543 | Typically, a tag is used to mark a special point such as the final change | 542 | Typically, a tag is used to mark a special point such as the final change |
544 | before a project is released. | 543 | before a project is released. |
545 | You can see the tags used with the <filename>poky</filename> Git repository | 544 | You can see the tags used with the <filename>poky</filename> Git repository |
546 | by going to <ulink url='http://git.yoctoproject.org/cgit.cgi/poky/'></ulink> and | 545 | by going to <ulink url='&YOCTO_GIT_URL;/cgit.cgi/poky/'></ulink> and |
547 | clicking on the | 546 | clicking on the |
548 | <filename><ulink url='http://git.yoctoproject.org/cgit.cgi/poky/refs/tags'>[...]</ulink></filename> | 547 | <filename><ulink url='&YOCTO_GIT_URL;/cgit.cgi/poky/refs/tags'>[...]</ulink></filename> |
549 | link beneath the "Tag" heading. | 548 | link beneath the "Tag" heading. |
550 | </para> | 549 | </para> |
551 | 550 | ||
552 | <para> | 551 | <para> |
553 | Some key tags are <filename>laverne-4.0</filename>, <filename>bernard-5.0</filename>, | 552 | Some key tags are <filename>laverne-4.0</filename>, <filename>bernard-5.0</filename>, |
554 | and <filename>edison-6.0</filename>. | 553 | and <filename>&DISTRO_NAME;-&POKYVERSION;</filename>. |
555 | These tags represent Yocto Project releases. | 554 | These tags represent Yocto Project releases. |
556 | </para> | 555 | </para> |
557 | 556 | ||
@@ -569,14 +568,14 @@ | |||
569 | $ cd ~ | 568 | $ cd ~ |
570 | $ git clone git://git.yoctoproject.org/poky | 569 | $ git clone git://git.yoctoproject.org/poky |
571 | $ cd poky | 570 | $ cd poky |
572 | $ git checkout edison-6.0 -b edison-6.0 | 571 | $ git checkout &DISTRO_NAME;-&POKYVERSION; -b &DISTRO_NAME;-&POKYVERSION; |
573 | </literallayout> | 572 | </literallayout> |
574 | In this example, the name of the top-level directory of your local Yocto Project | 573 | In this example, the name of the top-level directory of your local Yocto Project |
575 | Files Git repository is <filename>poky</filename>. | 574 | Files Git repository is <filename>poky</filename>. |
576 | And, the name of the local branch you have created and checked out is | 575 | And, the name of the local branch you have created and checked out is |
577 | <filename>edison-6.0</filename>. | 576 | <filename>&DISTRO_NAME;-&POKYVERSION;</filename>. |
578 | The files in your repository now exactly match the Yocto Project 1.1 | 577 | The files in your repository now exactly match the Yocto Project &DISTRO; |
579 | Release tag (edison). | 578 | Release tag (&DISTRO_NAME;). |
580 | It is important to understand that when you create and checkout a local | 579 | It is important to understand that when you create and checkout a local |
581 | working branch based on a tag, your environment matches a specific point | 580 | working branch based on a tag, your environment matches a specific point |
582 | in time and not a development branch. | 581 | in time and not a development branch. |
@@ -807,7 +806,7 @@ | |||
807 | changes, can be used to communicate changes and problems with developers, can be used to | 806 | changes, can be used to communicate changes and problems with developers, can be used to |
808 | submit and review patches, and can be used to manage quality assurance. | 807 | submit and review patches, and can be used to manage quality assurance. |
809 | The home page for the Yocto Project implementation of Bugzilla is | 808 | The home page for the Yocto Project implementation of Bugzilla is |
810 | <ulink url='http://bugzilla.yoctoproject.org'>http://bugzilla.yoctoproject.org</ulink>. | 809 | <ulink url='&YOCTO_BUGZILLA_URL;'>&YOCTO_BUGZILLA_URL;</ulink>. |
811 | </para> | 810 | </para> |
812 | 811 | ||
813 | <para> | 812 | <para> |
@@ -818,7 +817,7 @@ | |||
818 | Bugzilla. | 817 | Bugzilla. |
819 | You can find more information on defect management, bug tracking, and feature request | 818 | You can find more information on defect management, bug tracking, and feature request |
820 | processes all accomplished through the Yocto Project Bugzilla on the wiki page | 819 | processes all accomplished through the Yocto Project Bugzilla on the wiki page |
821 | <ulink url='https://wiki.yoctoproject.org/wiki/Bugzilla_Configuration_and_Bug_Tracking'>here</ulink>. | 820 | <ulink url='&YOCTO_WIKI_URL;/wiki/Bugzilla_Configuration_and_Bug_Tracking'>here</ulink>. |
822 | <orderedlist> | 821 | <orderedlist> |
823 | <listitem><para>Always use the Yocto Project implementation of Bugzilla to submit | 822 | <listitem><para>Always use the Yocto Project implementation of Bugzilla to submit |
824 | a bug.</para></listitem> | 823 | a bug.</para></listitem> |
@@ -866,7 +865,7 @@ | |||
866 | You should send patches to the appropriate Yocto Project mailing list to get them | 865 | You should send patches to the appropriate Yocto Project mailing list to get them |
867 | in front of the Yocto Project Maintainer. | 866 | in front of the Yocto Project Maintainer. |
868 | For a list of the Yocto Project mailing lists, see the | 867 | For a list of the Yocto Project mailing lists, see the |
869 | "<ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#resources-mailinglist'>Mailing lists</ulink>" section in | 868 | "<ulink url='&YOCTO_DOCS_REF_URL;#resources-mailinglist'>Mailing lists</ulink>" section in |
870 | The Yocto Project Reference Manual. | 869 | The Yocto Project Reference Manual. |
871 | </para> | 870 | </para> |
872 | 871 | ||
@@ -875,14 +874,14 @@ | |||
875 | <itemizedlist> | 874 | <itemizedlist> |
876 | <listitem><para>For defects against the Yocto Project build system Poky, send | 875 | <listitem><para>For defects against the Yocto Project build system Poky, send |
877 | your patch to the | 876 | your patch to the |
878 | <ulink url='http://lists.yoctoproject.org/listinfo/poky'></ulink> mailing list. | 877 | <ulink url='&YOCTO_LISTS_URL;/listinfo/poky'></ulink> mailing list. |
879 | This mailing list corresponds to issues that are not specific to the Yocto Project but | 878 | This mailing list corresponds to issues that are not specific to the Yocto Project but |
880 | are part of the OE-core. | 879 | are part of the OE-core. |
881 | For example, a defect against anything in the <filename>meta</filename> layer | 880 | For example, a defect against anything in the <filename>meta</filename> layer |
882 | or the BitBake Manual could be sent to this mailing list.</para></listitem> | 881 | or the BitBake Manual could be sent to this mailing list.</para></listitem> |
883 | <listitem><para>For defects against Yocto-specific layers, tools, and Yocto Project | 882 | <listitem><para>For defects against Yocto-specific layers, tools, and Yocto Project |
884 | documentation use the | 883 | documentation use the |
885 | <ulink url='http://lists.yoctoproject.org/listinfo/yocto'></ulink> mailing list. | 884 | <ulink url='&YOCTO_LISTS_URL;/listinfo/yocto'></ulink> mailing list. |
886 | This mailing list corresponds to Yocto-specific areas such as | 885 | This mailing list corresponds to Yocto-specific areas such as |
887 | <filename>meta-yocto</filename>, <filename>meta-intel</filename>, | 886 | <filename>meta-yocto</filename>, <filename>meta-intel</filename>, |
888 | <filename>linux-yocto</filename>, and <filename>documentation</filename>.</para></listitem> | 887 | <filename>linux-yocto</filename>, and <filename>documentation</filename>.</para></listitem> |
@@ -973,7 +972,7 @@ | |||
973 | <para> | 972 | <para> |
974 | You can find more guidance on creating well-formed commit messages at this OpenEmbedded | 973 | You can find more guidance on creating well-formed commit messages at this OpenEmbedded |
975 | wiki page: | 974 | wiki page: |
976 | <ulink url='http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines'></ulink>. | 975 | <ulink url='&OE_HOME_URL;/wiki/Commit_Patch_Message_Guidelines'></ulink>. |
977 | </para> | 976 | </para> |
978 | 977 | ||
979 | <para> | 978 | <para> |
@@ -1089,22 +1088,6 @@ | |||
1089 | </para> | 1088 | </para> |
1090 | </section> | 1089 | </section> |
1091 | </section> | 1090 | </section> |
1092 | |||
1093 | |||
1094 | |||
1095 | |||
1096 | |||
1097 | |||
1098 | |||
1099 | |||
1100 | |||
1101 | |||
1102 | |||
1103 | |||
1104 | |||
1105 | |||
1106 | |||
1107 | |||
1108 | </chapter> | 1091 | </chapter> |
1109 | <!-- | 1092 | <!-- |
1110 | vim: expandtab tw=80 ts=4 | 1093 | vim: expandtab tw=80 ts=4 |