diff options
| author |   Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-08-01 15:28:03 +0300 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-08-02 10:00:26 +0100 |
| commit | 4a226369b7bb37a971c77d4abc88df81033f56c5 (patch) | |
| tree | 534656b22f0d9b9ec71b163191da21b03f839716 /documentation | |
| parent | d283686dc3f785888c334594f4be0fd35c452def (diff) | |
| download | openembedded-core-contrib-4a226369b7bb37a971c77d4abc88df81033f56c5.tar.gz | |
dev-manual: Updates for checksums and wic
Accidentally put in a couple different things in this one commit.
Oh well.
1. New wording for how the user needs to figure out some checksums
for a recipe.
2. Fixed up some note placement in the wic reference section.
(From yocto-docs rev: 6c13f49c265c99ddd6dcd4ec3c3c8e66b78824e0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 47 |
1 files changed, 29 insertions, 18 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 4174d94527..5f8da23611 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1789,13 +1789,25 @@ </para> <para> - Ideally, you should locate these checksums from the upstream - website and use them in your recipe. - However, many websites do not provide the checksums. - If such is the case, you can use a "build-fail" method that - retrieves the exact strings you need. - To use the "build-fail" method, comment the statements out - and then attempt to build the software. + Finding proper values for <filename>md5</filename> and + <filename>sha256</filename> checksums can involve some work. + Initially, you should locate any available signatures from + the upstream source (i.e. <filename>md5</filename>, + <filename>sha1</filename>, <filename>sha256</filename>, + <filename>GPG</filename>, and so forth). + Because the OpenEmbedded build system only deals with + <filename>sha256sum</filename> and <filename>md5sum</filename>, + you should verify all the signatures you find by hand. + </para> + + <para> + After you have verified as many signatures as you can, + you can use a "build-fail" method that retrieves the exact + <filename>sha256sum</filename> and <filename>md5sum</filename> + checksums you need. + To use the "build-fail" method, comment the + <filename>SRC_URI</filename> statements out that provide the + checksums and then attempt to build the software. The build will produce an error for each missing checksum and as part of the error message provide the correct checksum string. @@ -4206,18 +4218,9 @@ <filename>partition</filename> (or <filename>part</filename> for short) and <filename>bootloader</filename>. <note> - <para> - Bootloader functionality and boot partitions are - implemented by the various - <filename>‐‐source</filename> - plugins that implement bootloader functionality. - The bootloader command essentially provides a means of - modifying bootloader configuration. - </para> - <para> Future updates will implement more commands and options. If you use anything that is not specifically - supported, results can be unpredictable.</para> + supported, results can be unpredictable. </note> </para> @@ -4364,7 +4367,15 @@ <para> This command specifies how the boot loader should be - and supports the following options: + configured and supports the following options: + <note> + Bootloader functionality and boot partitions are + implemented by the various + <filename>‐‐source</filename> + plugins that implement bootloader functionality. + The bootloader command essentially provides a means of + modifying bootloader configuration. + </note> <itemizedlist> <listitem><para><emphasis><filename>‐‐timeout</filename>:</emphasis> Specifies the number of seconds before the |