1
0
mirror of https://git.yoctoproject.org/poky synced 2026-06-02 01:19:52 +00:00

dev-manual: Removed tarball method for poky in setup section

Fixes [YOCTO #5368]

Partial fix for the bug.  This part removed the tarball install
method from the getting setup section of the second chapter. I
did some rewriting to smooth it out.

(From yocto-docs rev: b051433e34e0f3a46deba0b2b4815ab77fde62c8)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2013-10-29 07:37:31 -07:00
committed by Richard Purdie
parent 57d2417eac
commit 4d69fc1ad6
+32 -46
View File
@@ -79,47 +79,32 @@
them for the supported distributions. them for the supported distributions.
</para></listitem> </para></listitem>
<listitem id='local-yp-release'><para><emphasis>Yocto Project Release:</emphasis> <listitem id='local-yp-release'><para><emphasis>Yocto Project Release:</emphasis>
You need a release of the Yocto Project. You need a release of the Yocto Project installed locally on
You set that up with a local <link linkend='source-directory'>Source Directory</link> your development system.
one of two ways depending on whether you This local area is referred to as the
are going to contribute back into the Yocto Project or not. <link linkend='source-directory'>Source Directory</link>
<note> and is created when you use
Regardless of the method you use, this manual refers to the resulting local <link linkend='git'>Git</link> to clone a local copy
hierarchical set of files as the "Source Directory." of the upstream <filename>poky</filename> repository.</para>
<para>Working from a copy of the upstream repository allows you
to contribute back into the Yocto Project or simply work with
the latest software on a development branch.
Because Git maintains and creates an upstream repository with
a complete history of changes and you are working with a local
clone of that repository, you have access to all the Yocto
Project development branches and tag names used in the upstream
repository.</para>
<note>You can view the Yocto Project Source Repositories at
<ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink>
</note> </note>
<itemizedlist> <para>The following transcript shows how to clone the
<listitem><para><emphasis>Tarball Extraction:</emphasis> <filename>poky</filename> Git repository into the current
If you are not going to contribute back into the Yocto working directory.
Project, you can simply go to the The command creates the local repository in a directory
<ulink url='&YOCTO_HOME_URL;'>Yocto Project Website</ulink>, named <filename>poky</filename>.
select the "Downloads" tab, and choose what you want. For information on Git used within the Yocto Project, see
Once you have the tarball, just extract it into a the "<link linkend='git'>Git</link>" section.
directory of your choice.</para> <literallayout class='monospaced'>
<para>For example, the following command extracts the
Yocto Project &DISTRO; release tarball
into the current working directory and sets up the local Source Directory
with a top-level folder named <filename>&YOCTO_POKY;</filename>:
<literallayout class='monospaced'>
$ tar xfj &YOCTO_POKY_TARBALL;
</literallayout></para>
<para>This method does not produce a local Git repository.
Instead, you simply end up with a snapshot of the release.</para></listitem>
<listitem><para><emphasis>Git Repository Method:</emphasis> If you are going to be contributing
back into the Yocto Project or you simply want to keep up
with the latest developments, you should use Git commands to set up a local
Git repository of the upstream <filename>poky</filename> source repository.
Doing so creates a repository with a complete history of changes and allows
you to easily submit your changes upstream to the project.
Because you clone the repository, you have access to all the Yocto Project development
branches and tag names used in the upstream repository.</para>
<note>You can view the Yocto Project Source Repositories at
<ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink></note>
<para>The following transcript shows how to clone the <filename>poky</filename>
Git repository into the current working directory.
The command creates the local repository in a directory named <filename>poky</filename>.
For information on Git used within the Yocto Project, see the
"<link linkend='git'>Git</link>" section.
<literallayout class='monospaced'>
$ git clone git://git.yoctoproject.org/poky $ git clone git://git.yoctoproject.org/poky
Cloning into 'poky'... Cloning into 'poky'...
remote: Counting objects: 203728, done. remote: Counting objects: 203728, done.
@@ -127,12 +112,13 @@
remote: Total 203728 (delta 147444), reused 202891 (delta 146614) remote: Total 203728 (delta 147444), reused 202891 (delta 146614)
Receiving objects: 100% (203728/203728), 95.54 MiB | 308 KiB/s, done. Receiving objects: 100% (203728/203728), 95.54 MiB | 308 KiB/s, done.
Resolving deltas: 100% (147444/147444), done. Resolving deltas: 100% (147444/147444), done.
</literallayout></para> </literallayout></para>
<para>For another example of how to set up your own local Git repositories, see this <para>For another example of how to set up your own local Git
<ulink url='&YOCTO_WIKI_URL;/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP'> repositories, see this
wiki page</ulink>, which describes how to create both <filename>poky</filename> <ulink url='&YOCTO_WIKI_URL;/wiki/Transcript:_from_git_checkout_to_meta-intel_BSP'>
and <filename>meta-intel</filename> Git repositories.</para></listitem> wiki page</ulink>, which describes how to create both
</itemizedlist></para></listitem> <filename>poky</filename> and <filename>meta-intel</filename>
Git repositories.</para></listitem>
<listitem id='local-kernel-files'><para><emphasis>Yocto Project Kernel:</emphasis> <listitem id='local-kernel-files'><para><emphasis>Yocto Project Kernel:</emphasis>
If you are going to be making modifications to a supported Yocto Project kernel, you If you are going to be making modifications to a supported Yocto Project kernel, you
need to establish local copies of the source. need to establish local copies of the source.