Re: [PATCH 5/7] Usermanual/metadata: Fix documentation errors

[Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>]

On Wed, May 26, 2010 at 08:17:54AM +0200, Koen Kooi wrote:
>From: Chase Maupin <chase.maupin@ti.com>
>
>* Fixed up typos and other errors in the documentation.
>
>Signed-off-by: Chase Maupin <chase.maupin@ti.com>
>Signed-off-by: Koen Kooi <k-kooi@ti.com>
>---
> docs/usermanual/chapters/metadata.xml |   18 +++++++++---------
> 1 files changed, 9 insertions(+), 9 deletions(-)
>
>diff --git a/docs/usermanual/chapters/metadata.xml b/docs/usermanual/chapters/metadata.xml
>index bbf6f73..2b65454 100644
>--- a/docs/usermanual/chapters/metadata.xml
>+++ b/docs/usermanual/chapters/metadata.xml


Shouldn't the whole block below be updated to take SRC_URI[md5sum] and
SRC_URI[sha256sum] into account?

Alternatively just provide a link to
docs/usermanual/reference/var_src_uri.xml which covers that in detail
and should be more up-to-date

>@@ -128,23 +128,23 @@ DEPENDS = "gtk+"
> RDEPENDS = "cool-ttf-fonts"
>                 </screen> The package needs gtk+ to build ('DEPENDS') and
>     requires the 'cool-ttf-fonts' package to run ('RDEPENDS'). OE will add
>-    run-time dependencies on libraries on its own via the so called
>-    <emphasis>shlibs</emphasis>-code, but you need to specify everything other
>+        run-time dependencies on libraries on its own via the so called
>+    <emphasis>shlibs</emphasis>-code, but you need to specify everything else
>     by yourself, which in this case is the 'cool-ttf-fonts' package.</para>
> 
>     <para>After entering all this OE will know what to build before trying to
>     build your application, but it doesn't know where to get it yet. So let's
>     add the source location: <screen>
> SRC_URI = "http://www.host.com/foo/files/${P}.tar.bz2;md5sum=yoursum"
>-                </screen> This will tell the fetcher to where to download the
>+                </screen> This will tell the fetcher where to download the
>     sources from and it will check the integrity using md5sum if you provided
>     the appropriate <emphasis>yoursum</emphasis>. You can make one by doing
>     <screen>md5sum foo-1.9.tar.bz2</screen> and replacing
>     <emphasis>yoursum</emphasis> with the md5sum on your screen. A typical
>-    md5sum will look like this: <screen>a6434b0fc8a54c3dec3d6875bf3be8mtn </screen>Notice
>-    the <emphasis>${P}</emphasis> variable, that one holds the package name,
>-    <emphasis>${PN}</emphasis> in BitBake speak and the package version,
>-    <emphasis>${PV}</emphasis> in BitBake speak. It's a short way of writing
>+    md5sum will look like this: <screen>a6434b0fc8a54c3dec3d6875bf3be868 </screen>Notice
>+    the <emphasis>${P}</emphasis> variable holds the package name 
>+    (<emphasis>${PN}</emphasis> in BitBake speak) and the package version 
>+    (<emphasis>${PV}</emphasis> in BitBake speak). It's a short way of writing
>     <emphasis>${PN}-${PV}</emphasis>. Using this notation means you can copy
>     the recipe when a new version is released without having to alter the
>     contents. You do need to check if everything is still correct, because new