linux/poky.git/meta/classes, branch 1.9_M2

useradd_base.bbclass: do not warn when the user exists

2015-08-01T21:24:16+00:00

Use bbnote rather than bbwarn when the user exists, otherwise we would always get the warnings when rebuild the recipe or build with mulitlib, everything is OK if the user exists, so it should not be a warning. (From OE-Core rev: c0da4270c76375a7a8cbcc09319fe4570ebbc5bd) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

useradd_base.bbclass: print PN when bbnote/bbwarn/bbfatal

2015-08-01T21:24:16+00:00

Print PN will help debug: WARNING: openssh: user sshd already exists, not re-creating it Which is better than: WARNING: user sshd already exists, not re-creating it (From OE-Core rev: cfde8621d18967dee71042e02b8d6db5661df3da) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

base.bbclass/blacklist.bbclass: remove doc item when d.getVarFlags()

2015-08-01T21:24:16+00:00

The FOO[doc] is set in meta/conf/documentation.conf, we need remove it from d.getVarFlags()'s return dict when it causes many loops. (From OE-Core rev: 595a7af8d0a52b24e2bdb5c373c64d27b54bb25b) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

base.bbclass: move invalid PACKAGECONFIG checking to insane.bbclass

2015-08-01T21:24:15+00:00

There was a problem when check invalid PACKAGECONFIG in the anonymous function (when parsing), for example, there are two versions of a recipe: foo_1.0.bb foo_2.0.bb While foo_2.0.bb has a "PACKAGECONFIG[item] = 'x,y,z'", but foo_1.0.bb doesn't, if we set PACKAGECONFIG_pn-foo = "item" in a conf file, we would get the warning about invalid PACKAGECONFIG for foo_1.0.bb. Delay the checking to build time will fix the problem. [YOCTO #8065] (From OE-Core rev: 0a64dfcdb9f5a37771f881895be230392c4d0aff) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

populate_sdk_ext: pass BBPATH to devtool --bbpath

2015-08-01T21:24:12+00:00

(From OE-Core rev: 6ffb07715a289e2d3f57f4262beb92acb7280ea0) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

populate_sdk_ext: use lnr, not ln -sr, for portability

2015-08-01T21:24:12+00:00

Not all hosts are running sufficiently new coreutils. (From OE-Core rev: 3a813f277f8daa7686e26edc87f6a88724adde4e) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

base.bbclass: Note when including pn with INCOMPATIBLE_LICENSES

2015-08-01T21:24:08+00:00

We need to be able to tell people if we WHITELIST a recipe that contains an incompatible licese. Example: If we set WHITELIST_GPL-3.0 ?= "foo", foo will end up on an image even if GPL-3.0 is incompatible. This is the correct behaviour but there is nothing telling people that it is even happening. (From OE-Core rev: c9da529943b2f563b7b0aeb43576c13dd3b6f932) Signed-off-by: Beth Flanagan Signed-off-by: Richard Purdie

license_class: Fix choose_lic_set into incompatible license

2015-08-01T06:34:08+00:00

Use canonical_license when doing evaluation of license expresion since INCOMPATIBLE_LICENSE are already canonized. [YOCTO #8080] (From OE-Core rev: 799b25e09a149303edc1c098935f38a438878a95) Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

distrodata.bbclass: drop the manual upstream version check logic

2015-08-01T06:34:08+00:00

It's already taken care of in meta/lib/oe/recipeutils.py (From OE-Core rev: f7d0c03dc3cbfb79d22e1d89e31026a97c5b12ae) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

distrodata.bbclass: do not skip -native recipes in checkpkg task

2015-08-01T06:34:08+00:00

Some recipes are available only in the -native flavour, and we need to check their upstream version too from the command line. (From OE-Core rev: c63d1a544a3021a4eee2171fc710e71dfa7e6b07) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie