linux/poky.git/meta/lib/oe, branch 1.1_M3

lib/oe/util.py: Add MLPREFIX support to prune_suffix()

2011-07-27T15:18:50+00:00

prune_suffix() also needs be aware of MLPREFIX when changing PN for use in BPN. (From OE-Core rev: 20dd241052afa5ff80b91ebf09b0b48765bc3412) Signed-off-by: Richard Purdie

lib/oe/utils: 'Fix' oe.utils.contains() behaviour

2011-07-26T11:05:39+00:00

Currently oe.utils.contains(X, "A", true, false) will return true for substring matches, e.g. if X = "ABC". This is not what most users expect from the function. In the common OE use of this function there is the case of "touchscreen" and "screen" being used as independent variables. Whilst it could be argued there isn't a problem in that specific case (touchscreens are usually on screens), there is no substring usage of this function is OE-Core so this patch changes the behaviour to match only full strings. It also fixes a bug where duplicate entries would confuse multiple matches, e.g. contains(X, ["A", "B"], ...) would match X = "A A" which is clearly wrong. (From OE-Core rev: 5c09cbe3bf456e968fc853827698eb18b62e8348) Signed-off-by: Richard Purdie

oe.classutils: add module

2011-06-28T12:55:43+00:00

This adds a ClassRegistry utility metaclass, as maintaining a class registry is a fairly common thing to do. (From OE-Core rev: 6a46c375bea03b145bea41ec29ae2fd4d3cd9db6) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

packagedata.py: Fix read_subpkgdata_dict()

2011-06-23T15:02:40+00:00

If both VAR and VAR_foo are in subd, we need to ensure VAR_foo gets returned. Currently the code would work randomly. The only current user is the rpm packaging backend. (From OE-Core rev: ad098e40e8c57727892819e131bf18308bf244d2) Signed-off-by: Richard Purdie

packagedata: don't choke on empty PACKAGES

2011-05-20T18:07:51+00:00

(From OE-Core rev: 54ecf8e3992b8a01c2e5bd16720e1819b71b68bd) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Move packagedata code into oe.packagedata (sync from OE)

2011-05-20T18:07:51+00:00

(From OE-Core rev: e6858627ab087f2f25ebbd6c4422eeae35f3b0ac) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

oe.packagegroup: add code for package groups (sync from OE)

2011-05-20T18:07:51+00:00

This includes some utility functions for dealing with groups of packages defined in the metadata. Metadata syntax: PACKAGE_GROUP_ = "" If the packages in the group are optional: PACKAGE_GROUP_[optional] = "1" (From OE-Core rev: 4df212e9c2a1dd7c80d180fd13b67e9f2799d3e1) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

oe.data: expand the flags

2011-05-20T16:34:22+00:00

(From OE-Core rev: 8b9de6d2ad2d351bbc288cbb12562806ba8edae2) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Implement variable typing (sync from OE)

2011-05-20T16:34:22+00:00

This implementation consists of two components: - Type creation python modules, whose job it is to construct objects of the defined type for a given variable in the metadata - typecheck.bbclass, which iterates over all configuration variables with a type defined and uses oe.types to check the validity of the values This gives us a few benefits: - Automatic sanity checking of all configuration variables with a defined type - Avoid duplicating the "how do I make use of the value of this variable" logic between its users. For variables like PATH, this is simply a split(), for boolean variables, the duplication can result in confusing, or even mismatched semantics (is this 0/1, empty/nonempty, what?) - Make it easier to create a configuration UI, as the type information could be used to provide a better interface than a text edit box (e.g checkbox for 'boolean', dropdown for 'choice') This functionality is entirely opt-in right now. To enable the configuration variable type checking, simply INHERIT += "typecheck". Example of a failing type check: BAZ = "foo" BAZ[type] = "boolean" $ bitbake -p FATAL: BAZ: Invalid boolean value 'foo' $ Examples of leveraging oe.types in a python snippet: PACKAGES[type] = "list" python () { import oe.data for pkg in oe.data.typed_value("PACKAGES", d): bb.note("package: %s" % pkg) } LIBTOOL_HAS_SYSROOT = "yes" LIBTOOL_HAS_SYSROOT[type] = "boolean" python () { import oe.data assert(oe.data.typed_value("LIBTOOL_HAS_SYSROOT", d) == True) } (From OE-Core rev: a04ce490e933fc7534db33f635b025c25329c564) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Add a new task checklicense and fix some bugs in distro_check.py

2011-05-17T14:14:44+00:00

distro_check.py: Create a new function called create_log_file to reduce a lot of repeat code in distrodata.bbclass. We needn't to create log file in function save_distro_check_result, because the log file has been generated in check_eventhandler. Another bug is that we maybe access the /tmp/Meego-1.0 before we create this file. Add a judge statement to decide whether we need to create this file firstly. distrodata.bbclass: Add a new task checklicense to collect missing text license information. This can help package-report system to know how many recipes are missing license text. (From OE-Core rev: b41148cda9f0cc292b662a8473f26bc1ee0148f3) Signed-off-by: Mei Lei Signed-off-by: Richard Purdie