diff options
author | Lennart Johansson <lennart.johansson@enea.com> | 2016-06-20 10:14:23 +0200 |
---|---|---|
committer | Lennart Johansson <lennart.johansson@enea.com> | 2016-06-20 10:14:23 +0200 |
commit | d32acca7ab520ccbbb4b70304291a6db92f2e084 (patch) | |
tree | d9f02d7349f0b63f84165f1d3da7f775373d7b90 /doc/book-enea-linux-release-info/doc/getting_enea_linux.xml | |
parent | c8bef6fd9e4186f2907107102be646f49b0231b8 (diff) | |
download | el_releases-standard-d32acca7ab520ccbbb4b70304291a6db92f2e084.tar.gz |
First commit for el6 standard
Diffstat (limited to 'doc/book-enea-linux-release-info/doc/getting_enea_linux.xml')
-rw-r--r-- | doc/book-enea-linux-release-info/doc/getting_enea_linux.xml | 132 |
1 files changed, 132 insertions, 0 deletions
diff --git a/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml b/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml new file mode 100644 index 0000000..b356435 --- /dev/null +++ b/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml | |||
@@ -0,0 +1,132 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | ||
3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> | ||
4 | <chapter id="relinfo-getting-enea-linux"> | ||
5 | <title>Getting Enea Linux</title> | ||
6 | |||
7 | <section id="relinfo-getting-pre-built-images"> | ||
8 | <title>Getting Pre-built Binaries</title> | ||
9 | |||
10 | <para>Application developers will download pre-complied images from the | ||
11 | Enea Portal or will receive prebuilt images from the platform developers. | ||
12 | For further information on this see <olink | ||
13 | targetdoc="book_enea_linux_app_dev_guide" | ||
14 | targetptr="book_enea_linux_app_dev_guide">Enea Linux Application | ||
15 | Development Guide</olink>.</para> | ||
16 | </section> | ||
17 | |||
18 | <section id="relinfo-getting-source"> | ||
19 | <title>Getting the Source</title> | ||
20 | |||
21 | <para>The source for this Enea Linux release is available for cloning from | ||
22 | a set of Git repositories. To manage the different repositories, Google's | ||
23 | repo tool is used. The basic idea is to store a list with (repo-URL, | ||
24 | version) tuples in a separate file, known as the manifest. The repo tool | ||
25 | is then used to traverse the list and clone the specified versions of the | ||
26 | repositories. See <ulink | ||
27 | url="https://code.google.com/p/git-repo/">https://code.google.com/p/git-repo/</ulink> | ||
28 | for more info.</para> | ||
29 | |||
30 | <para>To use repo tool to download the source for Enea Linux, follow the | ||
31 | steps below:</para> | ||
32 | |||
33 | <orderedlist> | ||
34 | <listitem> | ||
35 | <para>Make sure that the repo tool is installed. If not, follow the | ||
36 | instructions below:</para> | ||
37 | |||
38 | <para><programlisting>$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo | ||
39 | $ chmod a+x ~/bin/repo</programlisting>The instruction assumes that ~/bin | ||
40 | exists and is included in the PATH variable.</para> | ||
41 | </listitem> | ||
42 | |||
43 | <listitem> | ||
44 | <para>Use the repo tool to download the source:<remark>FIXME: Before | ||
45 | final release the tag for the manifest must be set in Makefile as | ||
46 | MANIFESTHASH, typically something like refs/tags/EL6. Before that, a | ||
47 | generic branch name is used instead, e.g. krogoth in | ||
48 | Makefile</remark></para> | ||
49 | |||
50 | <para><programlisting>$ mkdir enea-linux | ||
51 | $ cd enea-linux | ||
52 | $ repo init -u <xi:include href="../../s_docsrc_common/pardoc-distro.xml" | ||
53 | xmlns:xi="http://www.w3.org/2001/XInclude" | ||
54 | xpointer="element(EneaLinux_MANIFESTURL/1)" /> \ | ||
55 | -b <xi:include href="../../s_docsrc_common/pardoc-distro.xml" | ||
56 | xmlns:xi="http://www.w3.org/2001/XInclude" | ||
57 | xpointer="element(EneaLinux_MANIFESTHASH/1)" /> \ | ||
58 | -m <manifest file> | ||
59 | $ repo sync</programlisting></para> | ||
60 | |||
61 | <para>The URI and 'refs/tags/EL6' specifies the location and version | ||
62 | of the repository where the manifest file is stored. The repo tool | ||
63 | assumes that the argument after '-b' is a branch, and to force | ||
64 | interpretation as a tag, the prefix refs/tags/ is needed.</para> | ||
65 | |||
66 | <para>The parameter <manifest file> depends on the target. See | ||
67 | the following table:</para> | ||
68 | |||
69 | <informaltable> | ||
70 | <tgroup cols="2"> | ||
71 | <thead> | ||
72 | <row> | ||
73 | <entry align="center">Target</entry> | ||
74 | |||
75 | <entry align="center">Manifest file</entry> | ||
76 | </row> | ||
77 | </thead> | ||
78 | |||
79 | <tbody> | ||
80 | <row> | ||
81 | <entry>P2041RDB</entry> | ||
82 | |||
83 | <entry><para>p2041rdb/default.xml</para></entry> | ||
84 | </row> | ||
85 | |||
86 | <row> | ||
87 | <entry>LS1021a-IoT</entry> | ||
88 | |||
89 | <entry><para>ls1021aiot/default.xml</para></entry> | ||
90 | </row> | ||
91 | |||
92 | <row> | ||
93 | <entry>QEMUARM</entry> | ||
94 | |||
95 | <entry><para>qemuarm/default.xml</para></entry> | ||
96 | </row> | ||
97 | |||
98 | <row> | ||
99 | <entry>QEMUPCC</entry> | ||
100 | |||
101 | <entry><para>qemuppc/default.xml</para></entry> | ||
102 | </row> | ||
103 | |||
104 | <row> | ||
105 | <entry>QEMUX86</entry> | ||
106 | |||
107 | <entry><para>qemux86/default.xml</para></entry> | ||
108 | </row> | ||
109 | </tbody> | ||
110 | </tgroup> | ||
111 | </informaltable> | ||
112 | </listitem> | ||
113 | </orderedlist> | ||
114 | |||
115 | <para>The source code is now downloaded. Current directory will contain a | ||
116 | README file with instructions on how to build the distro and boot the | ||
117 | target. For convenience, these instructions are also copied into this | ||
118 | document. See <xref linkend="relinfo-build-boot" />.</para> | ||
119 | |||
120 | <para>It is not necessary to explicitly clone the manifest repository | ||
121 | since that is done automatically by the repo tool. To see the current | ||
122 | manifest, e.g. to get a list of the repositories, use the following | ||
123 | command:</para> | ||
124 | |||
125 | <programlisting>$ repo manifest</programlisting> | ||
126 | |||
127 | <remark>The UG should be updated with instructions on how to add | ||
128 | customisations. That section should also contain some more info about the | ||
129 | manifest: The manifest templates, using a branch instead of the tag EL6, | ||
130 | ... When this is done a reference from here should be added.</remark> | ||
131 | </section> | ||
132 | </chapter> \ No newline at end of file | ||