linux/poky.git/meta/classes, branch 1.3_M4

classes/core-image: improve comments listing IMAGE_FEATURES

2012-09-06T23:07:44+00:00

Ensure this listing is complete. (Comment change only.) (From OE-Core rev: f9df0be3790ca837e43c41633d17e6ee851cb01d) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

gsettings.bbclass: fix whitespace

2012-09-05T21:25:23+00:00

As nothing in oe-core uses gsettings, it wasn't noticed that the whitespace is wrong. (From OE-Core rev: 1c2afda021f7abf88bc08400beba53c603912382) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

classes/qmake_base: support linux-gnuspe/linux-uclibcspe TARGET_OS

2012-09-05T16:32:14+00:00

Fix borrowed from OE-Classic. This should fix build failures during do_configure of Qt applications with the p1022ds machine from meta-fsl-ppc, for example. (From OE-Core rev: a19fc8e19a6cc6885a1e0616b1f42cc49c8f2c9f) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

sanity.bbclass: Move back to running at ConfigParsed time

2012-09-05T16:32:14+00:00

If we don't do this, users can get extremely confused errors since the sanity tests happen too late (after parsing) and don't see the warnings. Also cleanup messages about merging configuration file changes to give better hints at where the updated files may be. (From OE-Core rev: 7b8a68cda7ef8186e834b39e73ee12a55b33f85b) Signed-off-by: Richard Purdie

linux-yocto: check for bad SRCREV before branch checks

2012-09-04T13:46:17+00:00

do_validate_branches ensures that the desired SRCREV is at the tip of every branch that contains the revision. To do this, it looks for containing branches and processes them. This processing was mistakenly placed before the check for an invalid SRCREV, hence a git error message is seen in the log if a bad SRCREV is used, rather than a clear message. reordering the checks, and fixing a check for master, ensures that clear messages are generated in all cases. (From OE-Core rev: 7e4518bf88af53b09536a3bafcd4c392a094023f) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

linux-yocto: fix unapplied patch error message

2012-09-04T13:46:17+00:00

When patches fail to apply, the status of all pending patches should be exported to the logs and to the user. Currently, a missing export of GUILT_BASE makes it look more like an internal error, than a 'normal' patch failure: | [ERROR] unable to complete push | pending patches are: | Patches directory doesn't exist, try guilt-init With this variable exported, we have this: | [INFO] validating against known patches (qemux86-standard-meta) | error: patch failed: Makefile:2 | error: Makefile: patch does not apply | To force apply this patch, use 'guilt push -f' | [ERROR] unable to complete push | pending patches are: | links/files/0002-makefile-patch.patch (From OE-Core rev: b2b2512cbc4196fa0f814be3677517dab30e5b52) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

packagegroup-core-console: remove

2012-09-04T11:53:00+00:00

This provides one package group, packagegroup-core-apps-console, which is usually brought in by adding "apps-console-core" to IMAGE_FEATURES. Aside from the naming inconsistencies, this is a group of mostly unrelated packages, none of which are actually "apps". Handling each one: * dbus: should mostly be brought in by package runtime dependencies * avahi-daemon: if you are using packagegroup-base (as all images that inherit from core-image do) this is brought in by having "zeroconf" in DISTRO_FEATURES. * portmap: not very useful by itself; should be brought in by selecting NFS server/client through other means. * psplash (or whatever SPLASH is set to): this has been changed to be an explicit item "splash" in IMAGE_FEATURES. Since this is a fairly fundamental feature, a piece of code has been added to automatically handle this for images still using apps-console-core (and show a warning). (From OE-Core rev: 592d6e602466628d10704835a7b07d3d713f58e1) Signed-off-by: Paul Eggleton Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

packagegroup-core-qt: rename -demos to -demoapps

2012-09-04T11:53:00+00:00

Try to avoid confusion with the Qt demos distributed with Qt itself. (From OE-Core rev: dbbcc0cb9d2cbc66027c800075b94eb9b7110a00) Signed-off-by: Paul Eggleton Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

classes/packagegroup: disable superfluous tasks

2012-09-04T11:52:59+00:00

Disable tasks other than do_package* (similar to how image.bbclass disables everything except do_rootfs). This saves a little time as well as neatly avoiding the LIC_FILES_CHKSUM verification within do_configure which is not needed for package groups. (From OE-Core rev: fde2b0db798f03cf297a0d466a9c3a444f1321f3) Signed-off-by: Paul Eggleton Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

packagegroup-core-x11*: adjust X11 package groups

2012-09-04T11:52:58+00:00

Now the Sato pieces have been moved out, rebase packagegroup-core-x11 on packagegroup-x11-mini but using the structure/contents of meta-oe's task-x11 so that it can replace that; rename packagegroup-core-x11-mini to packagegroup-core-x11-base and pull in the xserver/utils packages via packagegroup-core-x11, and move both of these recipes under recipes-graphics. x11-mini is renamed to x11-base as it's what people should build on top of and since x11-mini is newer, the corresponding IMAGE_FEATURES item is less likely to be used in existing user recipes. (From OE-Core rev: 0cc9ced7d96b960994b0671095bc74becfc55e2c) Signed-off-by: Paul Eggleton Signed-off-by: Saul Wold Signed-off-by: Richard Purdie