Bug 13715 - Incorrect runall fetch command example in the development manual
Summary: Incorrect runall fetch command example in the development manual
Status: RESOLVED FIXED
Alias: None
Product: Development Manual
Classification: Documentation
Component: development (show other bugs)
Version: 2.6.4
Hardware: x86 Multiple
: High normal
Target Milestone: 3.1 M3
Assignee: Mark Morton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-12-19 15:36 UTC by Ahmed Hossam
Modified: 2020-03-12 14:47 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ahmed Hossam 2019-12-19 15:36:25 UTC
The runall fetch command example in chapter 3.23.2 (https://www.yoctoproject.org/docs/2.6.4/dev-manual/dev-manual.html#getting-source-files-and-suppressing-the-build) is incorrect
> $ bitbake -c target runall="fetch"
ERROR: Nothing PROVIDES 'runall=fetch'


The command in chapter 4.13.4 of the reference manual (https://www.yoctoproject.org/docs/2.6.4/ref-manual/ref-manual.html#migration-2.5-bitbake-changes) is the correct one:
> bitbake <target> --runall=fetch
Comment 1 Randy MacLeod 2020-02-13 15:52:57 UTC
Ping. M3 is in 2 weeks.
Comment 2 Mark Morton 2020-02-13 16:00:35 UTC
Got it - thanks for the reminder.
Comment 3 Richard Purdie 2020-02-21 14:00:43 UTC
I sent a patch for this and queued in master-next
Comment 5 Ahmed Hossam 2020-02-27 16:18:32 UTC
Is the '-c' needed (I have not tested that) ?
Comment 6 Ahmed Hossam 2020-02-29 06:25:21 UTC
I have tried the command and if I understand correctly -c interprets 'target' as a command so bitbake assumes that no target is passed and just prints a help message:

$ bitbake -c target --runall="fetch"
Nothing to do.  Use 'bitbake world' to build everything, or run 'bitbake --help' for usage information.
Comment 7 Richard Purdie 2020-03-01 16:48:02 UTC
You are correct, the -c should not be there either. I've fixed the patch queued in master-next to remove that.