linux/meta-openembedded.git/meta-python/conf, branch mickledore-net

ptest-packagelists-meta-python.inc: add ptest recipes

2023-04-04T20:39:45+00:00

Similar to ptest-packagelists.inc in oe-core, this list enables per image ptest (isolated ptests for a given recipe) * Add recipes to PTEST_FAST_META_PYTHON for ptests which take less than ~30s * Add recipes to PTEST_SLOW_META_PYTHON for ptests which take longer * Add recipes to PTEST_PROBLEMS_META_PYTHON for ptests which have failing tests or other issues with ptest package The initial list was taken from: meta_python_ptest_recipes=$(bitbake-layers show-recipes --recipes-only \ --layer meta-python --inherits ptest --bare | tr '\n' ' ' | \ pcregrep -o1 '^NOTE:.+===(.+)$') Signed-off-by: Tim Orling Signed-off-by: Khem Raj

layer.conf: update LAYERSERIES_COMPAT for mickledore

2023-01-04T22:34:04+00:00

* oe-core switched to mickedore in: https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f Signed-off-by: Khem Raj

layer.conf: Post release codename changes

2022-05-08T01:47:16+00:00

Post release add langdale to match core Signed-off-by: Armin Kuster Signed-off-by: Khem Raj

layer.conf: change layer priority to match oe-core

2022-02-28T16:39:26+00:00

Layer priority is the ultimate decider of what recipe is used: if layer A has recipe foo_1 and layer B has recipe foo_2, if layer A's priority is higher than B then foo_1 will be used, even though the version in B is higher, and even if PREFERRED_VERSION_foo is set to 2. This complicates recipes moving between layers, for example when a newer version of a recipe (say, python3-wheel) is taken from a layer with a higher priority (say, meta-python) and moved to a layer with a lower priority (say, oe-core) then it has to be removed before it is added: there is no way to have it in both layers and work correctly. Higher priorities are useful in distribution layers where you may want to override specific recipes without any other fuss. However as all of the layers in meta-oe simply add more recipes in defined areas, there's no need to have a higher layer priority. Signed-off-by: Ross Burton Signed-off-by: Khem Raj

layers: Bump to use kirkstone

2022-02-22T02:12:04+00:00

its not going to be backward ABI compatible with honister due to variable renaming. Signed-off-by: Khem Raj

layer.conf: Update to honister

2021-08-03T17:21:25+00:00

This marks the layers as compatible with honister now they use the new override syntax. Signed-off-by: Martin Jansa

layers: Drop gatesgarth from LAYERSERIES_COMPAT

2021-03-19T18:58:17+00:00

Signed-off-by: Khem Raj

layer.conf: Add hardknott to LAYERSERIES_COMPAT

2020-11-04T20:43:55+00:00

Thats codename for 3.3 Signed-off-by: Khem Raj

meta-openembedded: Add gatesgarth to LAYERSERIES_COMPAT

2020-10-15T18:42:15+00:00

Remove older releases from COMPAT Signed-off-by: Khem Raj

meta-python: depend on core version 12 or higher

2020-06-08T20:58:02+00:00

* python3-pyelftools and python3-pycryptodome(x) recipes were recently moved from meta-python to oe-core in: https://git.openembedded.org/meta-openembedded/commit/?id=7aee545a61c4f91d5e462d5b46b1b8f9a8bad1e3 https://git.openembedded.org/meta-openembedded/commit/?id=a8f3c00d8d113b46a49584682e10435157d516ca * core version was bumped now: https://git.openembedded.org/openembedded-core/commit/?id=2d503b27e7c88cee9a37c79c4605c77b11f230b6 * this dependency will make sure that people do upgrade oe-core when they do upgrade meta-python past these revisions, so the recipes won't suddenly disappear as a bonus they will get slightly newer version which are now in oe-core python3-pycryptodome(x) from 3.9.4 to 3.9.7: https://www.pycryptodome.org/en/latest/src/changelog.html#february-2020 python2-pyelftools from 0.25 to 0.26: https://github.com/eliben/pyelftools/commit/8a40f295bc36f96efeb8633dc4a5314f6077d0bf#diff-e4eb329834da3d36278b1b7d943b3bc9 Signed-off-by: Martin Jansa Signed-off-by: Khem Raj