This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer u
here:
http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#usingpoky-extend-customimage-custombb
one reads:
"One way to get additional software into an image is to create a
custom image. The following example shows the form for the two lines
you need:
IMAGE_INSTALL = "pack
Signed-off-by: Robert P. J. Day
---
given the length of chapter 5 in the dev manual, i'm going to do
this in bite-size pieces.
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml
b/documentation/dev-manual/dev-manual-common-tasks.xml
index 7d5063b..0ee7775 100644
--- a/documen
Signed-off-by: Robert P. J. Day
---
* is it technically correct to say there are now 5 BSPs? as in, does
genericx86-64 count as a new BSP distinct from genericx86? [aside: are
there any plans for a MIPS64 BSP?]
* if scott is up for it, a couple more variables for the variable
glossary might be
