* [PATCH] Yocto Project Dev Manual - bad reference in dev-manual-common-tasks.xml
@ 2012-04-13 21:59 Bob Cochran
2012-04-16 14:01 ` Rifenbark, Scott M
0 siblings, 1 reply; 2+ messages in thread
From: Bob Cochran @ 2012-04-13 21:59 UTC (permalink / raw)
To: Yocto discussion list
A reference to meta/recipes-sato/tasks/task-poky.bb is made as a good
example of a task; however, this file / recipe doesn't exist. I
replaced it with meta/recipes-core/tasks/task-core-boot.bb, which I
think is a both useful and basic example to consider.
Signed-off-by: Robert Cochran<yocto@mindchasers.com>
---
.../dev-manual/dev-manual-common-tasks.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml
b/documentation/dev-manual/dev-manual-common-tasks.xml
index a32085d..a81b656 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -495,7 +495,7 @@
For complex custom images, the best approach is to
create a custom task package
that is used to build the image or images.
A good example of a tasks package is
- <filename>meta/recipes-sato/tasks/task-poky.bb</filename>.
+
<filename>meta/recipes-core/tasks/task-core-boot.bb</filename>
The
<filename><ulink
url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'>PACKAGES</ulink></filename>
variable lists the task packages to build along with
the complementary
--
1.7.5.4
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] Yocto Project Dev Manual - bad reference in dev-manual-common-tasks.xml
2012-04-13 21:59 [PATCH] Yocto Project Dev Manual - bad reference in dev-manual-common-tasks.xml Bob Cochran
@ 2012-04-16 14:01 ` Rifenbark, Scott M
0 siblings, 0 replies; 2+ messages in thread
From: Rifenbark, Scott M @ 2012-04-16 14:01 UTC (permalink / raw)
To: Bob Cochran, Yocto discussion list
Robert,
Patch applied to the Development Manual. Thanks for submitting the change. For now, you can view the updated manual at http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html.
Scott
-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Bob Cochran
Sent: Friday, April 13, 2012 4:00 PM
To: Yocto discussion list
Subject: [yocto] [PATCH] Yocto Project Dev Manual - bad reference in dev-manual-common-tasks.xml
A reference to meta/recipes-sato/tasks/task-poky.bb is made as a good
example of a task; however, this file / recipe doesn't exist. I
replaced it with meta/recipes-core/tasks/task-core-boot.bb, which I
think is a both useful and basic example to consider.
Signed-off-by: Robert Cochran<yocto@mindchasers.com>
---
.../dev-manual/dev-manual-common-tasks.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml
b/documentation/dev-manual/dev-manual-common-tasks.xml
index a32085d..a81b656 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -495,7 +495,7 @@
For complex custom images, the best approach is to
create a custom task package
that is used to build the image or images.
A good example of a tasks package is
- <filename>meta/recipes-sato/tasks/task-poky.bb</filename>.
+
<filename>meta/recipes-core/tasks/task-core-boot.bb</filename>
The
<filename><ulink
url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'>PACKAGES</ulink></filename>
variable lists the task packages to build along with
the complementary
--
1.7.5.4
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply related [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-04-16 14:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-13 21:59 [PATCH] Yocto Project Dev Manual - bad reference in dev-manual-common-tasks.xml Bob Cochran
2012-04-16 14:01 ` Rifenbark, Scott M
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.