aboutsummaryrefslogtreecommitdiffstats
path: root/usermanual
diff options
context:
space:
mode:
authorMarcin Juszkiewicz <hrw@openembedded.org>2006-10-15 11:05:48 +0000
committerMarcin Juszkiewicz <hrw@openembedded.org>2006-10-15 11:05:48 +0000
commit1e1a3512b0968e01eea3832be9c315ad07215033 (patch)
tree01fbd596ff98d3b6772064069ef22355f1973dc1 /usermanual
parent0e0911d873d97a460d9442ca9bf6a29f653e1b46 (diff)
downloadopenembedded-1e1a3512b0968e01eea3832be9c315ad07215033.tar.gz
usermanual: rephrase 'getting OE' section, added info about 0.30 snapshot
Diffstat (limited to 'usermanual')
-rw-r--r--usermanual/usermanual.xml27
1 files changed, 22 insertions, 5 deletions
diff --git a/usermanual/usermanual.xml b/usermanual/usermanual.xml
index 020bd96f64..5298b1b6fd 100644
--- a/usermanual/usermanual.xml
+++ b/usermanual/usermanual.xml
@@ -201,18 +201,35 @@ Ausgecheckt, Revision 570.
The OpenEmbedded metadata has a high rate of development, so it's a good idea to stay up to date.
You'll need monotone 0.28 to get the metadata and stay up to date. Monotone is available in most distributions and has binaries at <ulink url="http://venge.net/monotone/">Monotone homepage</ulink>.
-<screen>
-#get the snapshot
+Next step is getting snapshot of database.
+
+<screen>
wget http://openembedded.org/snapshots/OE.mtn.bz2 http://openembedded.org/snapshots/OE.mtn.bz2.md5
+</screen>
+
+Or if you have monotone 0.30 or later:
+
+<screen>
+wget http://www.openembedded.org/snapshots/OE-this-is-for-mtn-0.30.mtn.bz2
+wget http://www.openembedded.org/snapshots/OE-this-is-for-mtn-0.30.mtn.bz2.md5
+</screen>
+
+Then verify integrity of snapshot by checking md5sum.
-#verify the integrity
+<screen>
cat OE.mtn.bz2.md5sum
md5sum OE.mtn.bz2
+</screen>
-#extract the tarball
+Then unpack database.
+
+<screen>
bunzip OE.mtn.bz2
+</screen>
+
+Finally checkout the development branch.
-#check the development branch
+<screen>
mtn --db=OE.mtn co -b org.openembedded.dev
</screen>