<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/bitbake/lib/bblayers/query.py, branch master-next</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=master-next</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=master-next'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2025-03-24T17:29:55+00:00</updated>
<entry>
<title>bitbake: Revert "bblayers/query: Fix using "removeprefix" string method"</title>
<updated>2025-03-24T17:29:55+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-03-20T16:54:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f502a9a10825515db66aa4b502a1411c32abc637'/>
<id>urn:sha1:f502a9a10825515db66aa4b502a1411c32abc637</id>
<content type='text'>
This reverts commit 004cfdec1c865f2351bbac99acb3d63bfef9d380.

Now we have python 3.9 as a minimum we can do this.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bblayers/query: Fix using "removeprefix" string method</title>
<updated>2025-02-21T13:14:22+00:00</updated>
<author>
<name>Joerg Schmidt</name>
<email>joerg.schmidt@garmin.com</email>
</author>
<published>2025-02-20T15:35:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ae8fe5b896a1f6bd0740d1fa6638b9d9377a8d28'/>
<id>urn:sha1:ae8fe5b896a1f6bd0740d1fa6638b9d9377a8d28</id>
<content type='text'>
The minimum Python version required for Yocto 5.0 is 3.8 which causes
failure in poky/bitbake/lib/bblayers/query.py when listing layers by
using command "bitbake-layers show-recipes -f --bare --mc MC" for the
given multiconfig MC.
The reason for that failure is the use of "removeprefix" string method
which got introduced in Python 3.9.
This patch replaces the "removeprefix" method with an equivalent
solution supported by Python 3.8.

(Bitbake rev: 004cfdec1c865f2351bbac99acb3d63bfef9d380)

Signed-off-by: Joerg Schmidt &lt;joerg.schmidt@garmin.com&gt;
Signed-off-by: Joshua Watt &lt;JPEWhacker@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: cooker: Make cooker 'skiplist' per-multiconfig/mc</title>
<updated>2024-12-17T11:48:25+00:00</updated>
<author>
<name>Chris Laplante</name>
<email>chris.laplante@agilent.com</email>
</author>
<published>2024-12-11T17:41:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9d1b31d2542e50afe8d832588a4858054278e66c'/>
<id>urn:sha1:9d1b31d2542e50afe8d832588a4858054278e66c</id>
<content type='text'>
Previously, the cooker skiplist was shared across multiconfigs
(including default ''). If you had a recipe that was incompatible with
several multiconfigs for different reasons, then the displayed reason
(i.e. the "ERROR: Nothing PROVIDES" and "* was skipped" messages) might
vary across invocations of bitbake. This was caused by the random order
in which recipes are parsed under different multiconfig contexts, with
each skip reason overwriting the previously assigned reason.

I hit this specificially when using COMPATIBLE_MACHINE, but
COMPATIBLE_HOST (or anything using bb.parse.SkipRecipe) would have done it too.

(Bitbake rev: c51f01a35ed9a928402eab0899598b5c59602eef)

Signed-off-by: Chris Laplante &lt;chris.laplante@agilent.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bblayers/query: Add multiconfig support to `show-appends`</title>
<updated>2023-08-16T08:43:49+00:00</updated>
<author>
<name>Joshua Watt</name>
<email>JPEWhacker@gmail.com</email>
</author>
<published>2023-08-15T16:11:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fb51e196a978d452e6a14a8343832659da97fdc7'/>
<id>urn:sha1:fb51e196a978d452e6a14a8343832659da97fdc7</id>
<content type='text'>
Adds a --mc argument to `bitbake-layers show-appends` so that users can
filter appends for a specific multiconfig (instead of always showing the
default configuration)

(Bitbake rev: f4dcbf114554c829467623b5587314d16ebdf3eb)

Signed-off-by: Joshua Watt &lt;JPEWhacker@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bblayers/query: Adjust show-layers output layout</title>
<updated>2023-02-04T17:03:15+00:00</updated>
<author>
<name>Pedro Baptista</name>
<email>pedro.miguel.baptista@gmail.com</email>
</author>
<published>2023-01-27T00:54:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=940cee8422eb7a002faaddbbab0b93d414ee413b'/>
<id>urn:sha1:940cee8422eb7a002faaddbbab0b93d414ee413b</id>
<content type='text'>
Increase the `ljust` value for each column in show-layers
output. This improves readability  when long layer paths are
included

(Bitbake rev: a56cd53e0e67a368acace9dab184bd94b9b67b1b)

Signed-off-by: Pedro Baptista &lt;pedro.miguel.baptista@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bblayers/query: Replace layer directory name with layer name for show-layers</title>
<updated>2023-02-04T17:03:15+00:00</updated>
<author>
<name>Pedro Baptista</name>
<email>pedro.miguel.baptista@gmail.com</email>
</author>
<published>2023-01-27T00:54:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9724df2861d55decdcb1618a9b2b64bef9ab9455'/>
<id>urn:sha1:9724df2861d55decdcb1618a9b2b64bef9ab9455</id>
<content type='text'>
Replace the layer directory name with the name from BBFILE_COLLECTIONS
which is useful when assigning a LAYERDEPENDS value

(Bitbake rev: 517cc3f5aee2a7d6362ce0202d4ee709a5378096)

Signed-off-by: Pedro Baptista &lt;pedro.miguel.baptista@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: BBHandler/cooker: Implement recipe and global classes</title>
<updated>2022-08-12T10:49:29+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-08-10T13:34:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7bd328f9d24b4fb23c7d5de50bddbb60828c9ffc'/>
<id>urn:sha1:7bd328f9d24b4fb23c7d5de50bddbb60828c9ffc</id>
<content type='text'>
We have some confusion for users since some classes are meant to work
in the configuration space (or "globally") and some are meant to be
selected by recipes individually.

The cleanest way I could find to clarify this is to create "classes-global"
and "classes-recipe" directories which contain the approproate classes and
have bitbake switch scope between them at the appropriate point during
parsing. The existing "classes" directory is always searched as a fallback.

Once a class is moved to a specific directory, it will no longer be found
in the incorrect context. A good example from OE is that

INHERIT += "testimage"

will no longer work but

IMAGE_CLASSES += "testimage"

will, which makes the global scope cleaner by only including it where it
is useful and intended to be used (images).

(Bitbake rev: f33ce7e742f46635658c400b82558cf822690b5e)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake: Add copyright headers where missing</title>
<updated>2022-08-12T10:49:29+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-08-10T19:58:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e19ce4191d94646e35386a5f2179c02ef8dc1cb6'/>
<id>urn:sha1:e19ce4191d94646e35386a5f2179c02ef8dc1cb6</id>
<content type='text'>
Where copyright headers were not present, add them to make things
clear.

(Bitbake rev: 1aa338a216350a2751fff52f866039343e9ac013)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake: fix regexp deprecation warnings</title>
<updated>2021-09-17T06:26:23+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2021-09-16T20:22:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=cee517568bfbf7d7eaddf197fbc1ed7d1c54c7e0'/>
<id>urn:sha1:cee517568bfbf7d7eaddf197fbc1ed7d1c54c7e0</id>
<content type='text'>
See here for details:
https://docs.python.org/3/library/re.html

(Bitbake rev: 660e6ad4abb77c6f3c1d48bd64777dd76c05d7e2)

Signed-off-by: Alexander Kanavin &lt;alex@linutronix.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake: bitbake-layers: add skip reason to output</title>
<updated>2021-08-23T07:30:54+00:00</updated>
<author>
<name>Marco Felsch</name>
<email>m.felsch@pengutronix.de</email>
</author>
<published>2021-08-17T08:25:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f113446f417711e652a01907ba14fc513861131e'/>
<id>urn:sha1:f113446f417711e652a01907ba14fc513861131e</id>
<content type='text'>
Currently we inform the user that some package/layer is skipped but we
don't print the reason albeit bitbake knows the reason. So currently it
looks like:

gtk+:
  meta-oe              2.24.32 (skipped)

With this change the output prints the skip reason which is very helpful
for debugging:

gtk+:
  meta-oe              2.24.32 (skipped: one of 'x11 directfb' needs to be in DISTRO_FEATURES)

(Bitbake rev: d43e72db4f7c8b47d91d99ed54ce30e9ee898de1)

Signed-off-by: Marco Felsch &lt;m.felsch@pengutronix.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
