linux/poky.git/meta/classes/base.bbclass, branch daisy-11.0.2

base.bbclass: Merge two ConfigParsed event handlers

2014-03-27T09:42:07+00:00

There were two ConfigParsed event handlers in base.bbclass, this merges them together for small efficiency wins. (From OE-Core rev: ff919ed132b543f70e9635be7a31f799aafcf8d6) Signed-off-by: Richard Purdie

base.bbclass: Run oe_import before other INHERITs

2014-03-27T09:42:06+00:00

Its possible for classes listed in INHERIT directives to use things like the oe.utils functions. If that happens the user sees a traceback since the modules don't become available until the ConfigParsed event. This change to use immediate expansion means that the oe modules become available much sooner and can be used in the core classes, including within base.bbclass. (From OE-Core rev: a9ecad713f37f2703e99c6b856207abeb6c5ad1f) Signed-off-by: Richard Purdie

base: Show PRINC value in the warning message

2014-03-05T17:36:36+00:00

* it's useful to know by how much we need to bump PR in original recipe to preserve upgrade path (From OE-Core rev: 6e1633eb246fee3dee154513efa410d0930ea386) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

base.bbclass: Deprecate the PRINC logic

2014-03-05T15:50:22+00:00

The PRINC logic is now deprecated, the PR server should be used to handle the automatic incrementing of the PR (package release) field. Add a warning message to alert users to the change. The functionality will be removed in the next release cycle. (From OE-Core rev: 6f8d01e0097ded355a1eb38724f11ee65401392e) Signed-off-by: Richard Purdie

base: Remove pointless createCopy/update_data calls

2014-02-28T14:01:11+00:00

I was asked why we had these copy and update_data calls. I can offer no good explanation other than them perhaps once being needed for reasons long since forgotten and superceeded. With modern bitbake these should not be needed and shouldn't have been for a long time. Lets therefore remove them and simplify the code. (From OE-Core rev: 33746924bea27e6f4d85898fe37d3e07d4317a3a) Signed-off-by: Richard Purdie Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

kernel.bbclass, base.bbclass: Fix support for old kernel configuration

2014-02-13T11:41:22+00:00

This solves a regression introduced by OE-Core:9b75f6a (kernel: use oldnoconfig before yes '' | make oldconfig). The original oe_runmake explicitly calls 'die' command in case of failure so the fallback code never runs. The fallback code needs to handle the oe_runmake return code to call the backward compatible callback so we introduced a new command called oe_runmake_call which is used by oe_runmake. This does not change the functional behaviour of oe_runmake so it avoids any change except for the code which does need to handle the oe_runmake exit code. (From OE-Core rev: 51707282fc2c5a74588b2d79b2229513a883924f) Signed-off-by: Otavio Salvador Signed-off-by: Richard Purdie

base bbclass: add support for lz4 compressed archives

2014-01-14T17:03:53+00:00

(From OE-Core rev: 8b31b2d612b7bcd98c393c3760bb2e1542c02bd5) Signed-off-by: Koen Kooi Signed-off-by: Richard Purdie

base.bbclass: pull in file-native for src.rpm

2014-01-06T22:17:33+00:00

Unpacking an src.rpm uses rpm2cpio.sh, which requires 'file'. Without this, builds of rpm on a host without 'file' installed will fail with very strange messages. (From OE-Core rev: 97e1d84e2d1a74791ce6af88ddc27963bc0e1bec) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

base/gcc-common: Ensure umask setting is consistent for shared workdir

2013-11-29T11:24:48+00:00

gcc has cross and target components with a shared workdir. The unpack umask settings need to match for all of these. We need to use strings in each case to ensure the sstate code matches them correctly. This patch tweaks various things to ensure the change adding the unpack umask change doesn't break the compiler builds. (From OE-Core rev: 67162438ee9c402b23c32853af9d313949eb6e4a) Signed-off-by: Richard Purdie

base.bbclass: Set umask 022 also for do_unpack task

2013-11-29T09:52:59+00:00

* when git checkouts files from fetched clone it respects system umask and creates files with different permissions, if such files are copied to packages, resulting target images have also different permissions on them. * we need reproducible builds across different builders with different system umask, so set 022 umask [YOCTO #5590] (From OE-Core rev: c9289c506633ffe5c482000d8d225e45454c064d) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie