summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-newbie.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual/dev-manual-newbie.xml')
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml52
1 files changed, 24 insertions, 28 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 34326d10b6..0ba560854d 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -406,38 +406,34 @@
406 <title>Yocto Project Source Repositories</title> 406 <title>Yocto Project Source Repositories</title>
407 407
408 <para> 408 <para>
409 The Yocto Project team maintains complete source repositories for all Yocto Project files 409 The Yocto Project team maintains complete source repositories for all
410 at <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi'></ulink>. 410 Yocto Project files at
411 This web-based source code browser is organized into categories by function such as 411 <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi'></ulink>.
412 IDE Plugins, Matchbox, Poky, Yocto Linux Kernel, and so forth. 412 This web-based source code browser is organized into categories by
413 From the interface, you can click on any particular item in the "Name" column and 413 function such as IDE Plugins, Matchbox, Poky, Yocto Linux Kernel, and
414 see the URL at the bottom of the page that you need to clone a Git repository for 414 so forth.
415 that particular item. 415 From the interface, you can click on any particular item in the "Name"
416 Having a local Git repository of the Source Directory (poky) allows you to 416 column and see the URL at the bottom of the page that you need to clone
417 make changes, contribute to the history, and ultimately enhance the Yocto Project's 417 a Git repository for that particular item.
418 tools, Board Support Packages, and so forth. 418 Having a local Git repository of the Source Directory (poky) allows
419 you to make changes, contribute to the history, and ultimately enhance
420 the Yocto Project's tools, Board Support Packages, and so forth.
419 </para> 421 </para>
420 422
421 <para> 423 <para>
422 Conversely, if you are a developer that is not interested in contributing back to the 424 For any supported release of Yocto Project, you can also go to the
423 Yocto Project, you have the ability to simply download and extract release tarballs
424 and use them within the Yocto Project environment.
425 All that is required is a particular release of the Yocto Project and
426 your application source code.
427 </para>
428
429 <para>
430 For any supported release of Yocto Project, you can go to the
431 <ulink url='&YOCTO_HOME_URL;'>Yocto Project Website</ulink> and 425 <ulink url='&YOCTO_HOME_URL;'>Yocto Project Website</ulink> and
432 select the "Downloads" tab and get a tarball of the release. 426 select the "Downloads" tab and get a released tarball of the
433 You can also go to this site to download any supported BSP tarballs. 427 <filename>poky</filename> repository or any supported BSP tarballs.
434 Unpacking the tarball gives you a hierarchical Source Directory that lets you develop 428 Unpacking these tarballs gives you a snapshot of the released
435 using the Yocto Project. 429 files.
436 </para> 430 <note>
437 431 The recommended method for setting up the Yocto Project
438 <para> 432 <link linkend='source-directory'>Source Directory</link> and the
439 Once you are set up through either tarball extraction or a checkout of Git repositories, 433 files for supported BSPs (<filename>meta-intel</filename>) is to
440 you are ready to develop. 434 use <link linkend='git'>Git</link> to create a local copy of the
435 upstream repositories.
436 </note>
441 </para> 437 </para>
442 438
443 <para> 439 <para>