summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-common-tasks.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-07-31 09:42:48 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-08-02 10:00:25 +0100
commit25d7b0df2a2d0a7ee46b93df1d92735aa04a7b44 (patch)
tree0351b69353ac58afe4a55f068458d3b6c187f91e /documentation/dev-manual/dev-manual-common-tasks.xml
parent3be4af9cf3a517183aafd8db1ab4b568679baa93 (diff)
downloadpoky-25d7b0df2a2d0a7ee46b93df1d92735aa04a7b44.tar.gz
dev-manual: Modified how to find checksums in the recipes
The section on wrting a new recipe suggested using a "build-fail" method to get bitbake to return exact checksums for code. It was pointed out that this could be a middle-security risk and that we should not do that but instead get the signatures from the upstream website. However, many times those sites don't provide that information. I re-worded the text to note the ideal method (upstream checksums) and then resorted to the "build-fail" method as a "way" to also get them when the upstream location does not have them. (From yocto-docs rev: b06699de2f512b01600bf952a8ee928c2a4c358a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml7
1 files changed, 6 insertions, 1 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index d235a99f91..8f7c6d9269 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1789,7 +1789,12 @@
1789 </para> 1789 </para>
1790 1790
1791 <para> 1791 <para>
1792 To find these checksums, you can comment the statements out 1792 Ideally, you should locate these checksums from the upstream
1793 website and use them in your recipe.
1794 However, many websites do not provide the checksums.
1795 If such is the case, you can use a "build-fail" method that
1796 retrieves the exact strings you need.
1797 To use the "build-fail" method, comment the statements out
1793 and then attempt to build the software. 1798 and then attempt to build the software.
1794 The build will produce an error for each missing checksum 1799 The build will produce an error for each missing checksum
1795 and as part of the error message provide the correct checksum 1800 and as part of the error message provide the correct checksum