diff options
Diffstat (limited to 'documentation/dev-manual/start.rst')
-rw-r--r-- | documentation/dev-manual/start.rst | 26 |
1 files changed, 9 insertions, 17 deletions
diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst index 18fd8ccf60..c3276c9502 100644 --- a/documentation/dev-manual/start.rst +++ b/documentation/dev-manual/start.rst | |||
@@ -36,7 +36,7 @@ particular working environment and set of practices. | |||
36 | equipment together and set up your development environment's | 36 | equipment together and set up your development environment's |
37 | hardware topology. | 37 | hardware topology. |
38 | 38 | ||
39 | The following roles exist: | 39 | Here are possible roles: |
40 | 40 | ||
41 | - *Application Developer:* This type of developer does application | 41 | - *Application Developer:* This type of developer does application |
42 | level work on top of an existing software stack. | 42 | level work on top of an existing software stack. |
@@ -99,8 +99,7 @@ particular working environment and set of practices. | |||
99 | .. note:: | 99 | .. note:: |
100 | 100 | ||
101 | The setup of these services is beyond the scope of this manual. | 101 | The setup of these services is beyond the scope of this manual. |
102 | However, sites such as the following exist that describe how to | 102 | However, here are sites describing how to perform setup: |
103 | perform setup: | ||
104 | 103 | ||
105 | - `Gitolite <https://gitolite.com>`__: Information for | 104 | - `Gitolite <https://gitolite.com>`__: Information for |
106 | ``gitolite``. | 105 | ``gitolite``. |
@@ -190,7 +189,7 @@ particular working environment and set of practices. | |||
190 | develop locally using their primary development system. | 189 | develop locally using their primary development system. |
191 | 190 | ||
192 | 9. *Document Policies and Change Flow:* The Yocto Project uses a | 191 | 9. *Document Policies and Change Flow:* The Yocto Project uses a |
193 | hierarchical structure and a pull model. Scripts exist to create and | 192 | hierarchical structure and a pull model. There are scripts to create and |
194 | send pull requests (i.e. ``create-pull-request`` and | 193 | send pull requests (i.e. ``create-pull-request`` and |
195 | ``send-pull-request``). This model is in line with other open source | 194 | ``send-pull-request``). This model is in line with other open source |
196 | projects where maintainers are responsible for specific areas of the | 195 | projects where maintainers are responsible for specific areas of the |
@@ -215,8 +214,8 @@ particular working environment and set of practices. | |||
215 | someone else in the community needs them also. | 214 | someone else in the community needs them also. |
216 | 215 | ||
217 | 10. *Development Environment Summary:* Aside from the previous steps, | 216 | 10. *Development Environment Summary:* Aside from the previous steps, |
218 | some best practices exist within the Yocto Project development | 217 | here are best practices within the Yocto Project development |
219 | environment. Consider the following: | 218 | environment: |
220 | 219 | ||
221 | - Use :ref:`overview-manual/development-environment:git` as the source control | 220 | - Use :ref:`overview-manual/development-environment:git` as the source control |
222 | system. | 221 | system. |
@@ -607,8 +606,8 @@ of a given component. | |||
607 | 606 | ||
608 | The recommended method for accessing Yocto Project components is to | 607 | The recommended method for accessing Yocto Project components is to |
609 | use Git to clone the upstream repository and work from within that | 608 | use Git to clone the upstream repository and work from within that |
610 | locally cloned repository. The procedure in this section exists | 609 | locally cloned repository. However, this section documents how to |
611 | should you desire a tarball snapshot of any given component. | 610 | use a tarball snapshot of any given component. |
612 | 611 | ||
613 | Follow these steps to locate and download a particular tarball: | 612 | Follow these steps to locate and download a particular tarball: |
614 | 613 | ||
@@ -645,13 +644,6 @@ release. Rather than Git repositories, these files represent snapshot | |||
645 | tarballs similar to the tarballs located in the Index of Releases | 644 | tarballs similar to the tarballs located in the Index of Releases |
646 | described in the ":ref:`dev-manual/start:accessing index of releases`" section. | 645 | described in the ":ref:`dev-manual/start:accessing index of releases`" section. |
647 | 646 | ||
648 | .. note:: | ||
649 | |||
650 | The recommended method for accessing Yocto Project components is to | ||
651 | use Git to clone a repository and work from within that local | ||
652 | repository. The procedure in this section exists should you desire a | ||
653 | tarball snapshot of any given component. | ||
654 | |||
655 | 1. *Go to the Yocto Project Website:* Open The | 647 | 1. *Go to the Yocto Project Website:* Open The |
656 | :yocto_home:`Yocto Project Website <>` in your browser. | 648 | :yocto_home:`Yocto Project Website <>` in your browser. |
657 | 649 | ||
@@ -750,8 +742,8 @@ Follow these steps to create a local version of the upstream | |||
750 | ":ref:`dev-manual/start:checking out by tag in poky`" sections, respectively. | 742 | ":ref:`dev-manual/start:checking out by tag in poky`" sections, respectively. |
751 | 743 | ||
752 | Once the local repository is created, you can change to that | 744 | Once the local repository is created, you can change to that |
753 | directory and check its status. Here, the single "master" branch | 745 | directory and check its status. The ``master`` branch is checked out |
754 | exists on your system and by default, it is checked out:: | 746 | by default:: |
755 | 747 | ||
756 | $ cd poky | 748 | $ cd poky |
757 | $ git status | 749 | $ git status |