diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-10-30 08:09:53 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-11-01 17:09:58 +0000 |
commit | 08b5e3129c84bf5694fc1785775b43c7e2ee16ce (patch) | |
tree | a1e14d23a05e57178fc65dffae8f655e9963af52 /documentation | |
parent | 0ef2170a2b6ebe3fe075c6d6c1948de9dfe792b8 (diff) | |
download | poky-08b5e3129c84bf5694fc1785775b43c7e2ee16ce.tar.gz |
ref-manual: updated the list of where to get YP release
Partial fix for [YOCTO #5368]
The list that summarized where to get YP release did not include
the source repositories. It basically just listed tarball
areas. Now that cloning the Git repo of poky is the preferred
method for obtaining YP, I made sure that this area was the
first spot listed and called out as the preferred method.
(From yocto-docs rev: d5aabd2cb70ea7b7caf5f39d0630ba6961280e1a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/ref-manual/introduction.xml | 30 |
1 files changed, 23 insertions, 7 deletions
diff --git a/documentation/ref-manual/introduction.xml b/documentation/ref-manual/introduction.xml index 3e071baebd..18363d48dd 100644 --- a/documentation/ref-manual/introduction.xml +++ b/documentation/ref-manual/introduction.xml | |||
@@ -409,16 +409,32 @@ | |||
409 | The Yocto Project development team makes the Yocto Project available through a number | 409 | The Yocto Project development team makes the Yocto Project available through a number |
410 | of methods: | 410 | of methods: |
411 | <itemizedlist> | 411 | <itemizedlist> |
412 | <listitem><para><emphasis>Releases:</emphasis> Stable, tested releases are available through | 412 | <listitem><para><emphasis>Source Repositories:</emphasis> |
413 | Working from a copy of the upstream | ||
414 | <filename>poky</filename> repository is the | ||
415 | preferred method for obtaining and using a Yocto Project | ||
416 | release. | ||
417 | You can view the Yocto Project Source Repositories at | ||
418 | <ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink>. | ||
419 | In particular, you can find the | ||
420 | <filename>poky</filename> repository at | ||
421 | <ulink url='http://git.yoctoproject.org/cgit/cgit.cgi/poky/'></ulink>. | ||
422 | </para></listitem> | ||
423 | <listitem><para><emphasis>Releases:</emphasis> Stable, tested | ||
424 | releases are available as tarballs through | ||
413 | <ulink url='&YOCTO_DL_URL;/releases/yocto/'/>.</para></listitem> | 425 | <ulink url='&YOCTO_DL_URL;/releases/yocto/'/>.</para></listitem> |
414 | <listitem><para><emphasis>Nightly Builds:</emphasis> These releases are available at | 426 | <listitem><para><emphasis>Nightly Builds:</emphasis> These |
427 | tarball releases are available at | ||
415 | <ulink url='http://autobuilder.yoctoproject.org/nightly'/>. | 428 | <ulink url='http://autobuilder.yoctoproject.org/nightly'/>. |
416 | These builds include Yocto Project releases, meta-toolchain tarball installation scripts, and | 429 | These builds include Yocto Project releases, meta-toolchain |
417 | experimental builds.</para></listitem> | 430 | tarball installation scripts, and experimental builds. |
418 | <listitem><para><emphasis>Yocto Project Website:</emphasis> You can find releases | 431 | </para></listitem> |
419 | of the Yocto Project and supported BSPs at the | 432 | <listitem><para><emphasis>Yocto Project Website:</emphasis> You can |
433 | find tarball releases of the Yocto Project and supported BSPs | ||
434 | at the | ||
420 | <ulink url='&YOCTO_HOME_URL;'>Yocto Project website</ulink>. | 435 | <ulink url='&YOCTO_HOME_URL;'>Yocto Project website</ulink>. |
421 | Along with these downloads, you can find lots of other information at this site. | 436 | Along with these downloads, you can find lots of other |
437 | information at this site. | ||
422 | </para></listitem> | 438 | </para></listitem> |
423 | </itemizedlist> | 439 | </itemizedlist> |
424 | </para> | 440 | </para> |