summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/start.rst45
1 files changed, 12 insertions, 33 deletions
diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst
index 27fc0fcd01..4881481044 100644
--- a/documentation/dev-manual/start.rst
+++ b/documentation/dev-manual/start.rst
@@ -613,44 +613,23 @@ Use the following procedure to locate the latest upstream copy of the
613 For information on cloning a repository, see the 613 For information on cloning a repository, see the
614 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`" section. 614 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`" section.
615 615
616Accessing Index of Releases 616Accessing Source Archives
617--------------------------- 617-------------------------
618
619The Yocto Project also provides source archives of its releases, which
620are available on :yocto_dl:`/releases/yocto/`. Then, choose the subdirectory
621containing the release you wish to use, for example
622:yocto_dl:`yocto-&DISTRO; </releases/yocto/yocto-&DISTRO;/>`.
618 623
619Yocto Project maintains an Index of Releases area that contains related 624You will find there source archives of individual components (if you wish
620files that contribute to the Yocto Project. Rather than Git 625to use them individually), and of the corresponding Poky release bundling
621repositories, these files are tarballs that represent snapshots in time 626a selection of these components.
622of a given component.
623 627
624.. note:: 628.. note::
625 629
626 The recommended method for accessing Yocto Project components is to 630 The recommended method for accessing Yocto Project components is to
627 use Git to clone the upstream repository and work from within that 631 use Git to clone the upstream repository and work from within that
628 locally cloned repository. However, this section documents how to 632 locally cloned repository.
629 use a tarball snapshot of any given component.
630
631Follow these steps to locate and download a particular tarball:
632
633#. *Access the Index of Releases:* Open a browser and go to
634 :yocto_dl:`Index of Releases </releases>`. The
635 list represents released components (e.g. ``bitbake``, ``sato``, and
636 so on).
637
638 .. note::
639
640 The ``yocto`` directory contains the full array of released Poky
641 tarballs. The ``poky`` directory in the Index of Releases was
642 historically used for very early releases and exists now only for
643 retroactive completeness.
644
645#. *Select a Component:* Click on any released component in which you
646 are interested (e.g. ``yocto``).
647
648#. *Find the Tarball:* Drill down to find the associated tarball. For
649 example, click on ``yocto-&DISTRO;`` to view files associated with the
650 Yocto Project &DISTRO; release.
651
652#. *Download the Tarball:* Click the tarball to download and save a
653 snapshot of the given component.
654 633
655Using the Downloads Page 634Using the Downloads Page
656------------------------ 635------------------------
@@ -659,7 +638,7 @@ The :yocto_home:`Yocto Project Website <>` uses a "DOWNLOADS" page
659from which you can locate and download tarballs of any Yocto Project 638from which you can locate and download tarballs of any Yocto Project
660release. Rather than Git repositories, these files represent snapshot 639release. Rather than Git repositories, these files represent snapshot
661tarballs similar to the tarballs located in the Index of Releases 640tarballs similar to the tarballs located in the Index of Releases
662described in the ":ref:`dev-manual/start:accessing index of releases`" section. 641described in the ":ref:`dev-manual/start:accessing source archives`" section.
663 642
664#. *Go to the Yocto Project Website:* Open The 643#. *Go to the Yocto Project Website:* Open The
665 :yocto_home:`Yocto Project Website <>` in your browser. 644 :yocto_home:`Yocto Project Website <>` in your browser.