linux/poky.git/meta/classes/distrodata.bbclass, branch master

distrodata: Remove

2018-12-18T16:19:34+00:00

The code in the tasks within this class are old and there are much better ways to do these things now such as through tinfoil rather than writing csv files incrementally with start/stop events and lock files. Existing users of the code (mainly the do_checkpkg task) have been ported over to tinfoil. Drop the class, any other users should also make use of the tinfoil functionality. (From OE-Core rev: 6e2a488f01e5e8bc6f06b6fac1d336bf5372a82b) Signed-off-by: Richard Purdie

upstream-tracking.inc: Remove the long deprecated file

2018-12-18T16:19:34+00:00

(From OE-Core rev: 22447eba250656489a6ed636fe58cb304d74e975) Signed-off-by: Richard Purdie

defaultsetup: Include maintainers.inc by default

2018-12-18T16:19:34+00:00

There is little harm in including this file rather than having a rather obscure and soon to be obsolete bbclass adding this information. (From OE-Core rev: 98536be8d1a5dcf620ee6d07135f23126a09d98f) Signed-off-by: Richard Purdie

distrodata: remove redudant *all tasks now that --runall works correctly

2018-02-16T18:05:40+00:00

(From OE-Core rev: 120dc59ad4a9ca232176c8a09bb3e43a9d1e24ac) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

distrodata.bbclass: make upstream version check more useful for git upstreams

2017-11-30T10:49:22+00:00

Specifically: 1) remove +git${SRCPV} stuff from comparison and output; it's just unnecessary clutter; 2) write the commit id of the latest version tag into the output; this saves quite a bit of trouble of manually checking what that commit id is when doing version updates; 3) when UPSTREAM_CHECK_COMMITS is set, ignore the tags altogether; instead check if the latest commit is different to the one we use, and if so, report that the recipe can be updated to said commit (which is also written into the output, as in 2). Multiple recipes are failing the upstream check because they never issue tags, now we can fix them. (From OE-Core rev: 591d57877d3d3e659d78c0ed33f4c515e3f6f8fb) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

distrodata.bbclass: add UPSTREAM_VERSION_UNKNOWN and UPSTREAM_CHECK_UNRELIABLE

2017-08-15T23:03:13+00:00

These are optional per-recipe variables with the following meaning: UPSTREAM_VERSION_UNKNOWN - set if the upstream version check fails reliably, e.g. absent git tags, or weird version format used on our or on upstream side. If this variable is not set and version check fails, or if it is set and the version check succeeds, then the checkpkg selftest for the recipe will fail. UPSTREAM_CHECK_UNRELIABLE - set if the upstream check cannot be reliably performed due to transient network failures, or server behaving weirdly. This one should be used sparingly, as it completely excludes a recipe from upstream checking, and thus we don't get automatically notified about new upstream releases. Also the upstream status string in the checkpkg csv output is clarified with the following possible values: MATCH - recipe is providing the latest upstream version UPDATE - there is a new version released by upstream, recipe should be updated CHECK_IS_UNRELIABLE - an upstream check was skipped as requested by recipe via UPSTREAM_CHECK_UNRELIABLE UNKNOWN - upstream version check was performed, but the upstream verison could not be determined. The recipe acknowledges this via UPSTREAM_VERSION_UNKNOWN setting. UNKNWON_BROKEN - same as previous, but the recipe does not include the acknowledgement and should be fixed. KNOWN_BROKEN - upstream check worked, but recipe claims it shouldn't; to fix this remove UPSTREAM_VERSION_UNKNOWN from recipe. [YOCTO #11896] (From OE-Core rev: 2a44ac1add0338cd7ff012cda96bf113c9a01bd6) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

classes: Drop now unneeded update_data calls

2017-02-15T17:29:55+00:00

Now that the datastore works dynamically we don't need the update_data calls so we can just remove them. They're not actually done anything at all for a while. (From OE-Core rev: 8de0c5d3bd01919e2bf0394f9c485936d6098cec) Signed-off-by: Richard Purdie

distrodata: add DATETIME to vardepsexclude for do_distro_check.

2017-01-31T14:43:00+00:00

This task uses DATETIME so add it to vardepsexclude so bitbake doesn't refuse to execute the task when the time changes between the controller and the worker calculating the hash. [ YOCTO #10960 ] (From OE-Core rev: e6784ef0d56a1b297001bc59c0da3aecebd1c656) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta: remove True option to getVar calls

2016-12-16T10:23:23+00:00

getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?$( ?[^,()]*), True$ (From OE-Core rev: 7c552996597faaee2fbee185b250c0ee30ea3b5f) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

package_regex.inc: remove deprecated file

2016-05-19T21:32:07+00:00

Remove this file as it has been deprecated in the previous release. New entries should be added to recipes itself. (From OE-Core rev: a3075bf29f0fa80489e3dd2ade65cc3a3b3d0332) Signed-off-by: Maxin B. John Signed-off-by: Richard Purdie