Mirror of git.openembedded.org/meta-openembedded https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=mickledore-net 2023-01-04T22:34:04+00:00 2023-01-04T22:34:04+00:00 Martin Jansa martin.jansa@gmail.com 2023-01-03T16:06:09+00:00 urn:sha1:84ffd15cd1f77da445c9900a2d08892cd58f3313 * oe-core switched to mickedore in: https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f Signed-off-by: Khem Raj <raj.khem@gmail.com> 2022-05-08T01:47:16+00:00 Armin Kuster akuster808@gmail.com 2022-04-27T22:07:37+00:00 urn:sha1:71bbe89bac6c7b2788e92932e3ea271cf5cbb5bc Post release add langdale to match core Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2022-02-28T16:39:26+00:00 Ross Burton ross.burton@arm.com 2022-02-25T11:06:27+00:00 urn:sha1:272f2083d46a5a023d0d18dcd3e8540a7c5c1cc8 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 <ross.burton@arm.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> 2022-02-22T02:12:04+00:00 Khem Raj raj.khem@gmail.com 2022-02-17T20:38:16+00:00 urn:sha1:d9ec74d4c29fa3020d95a2ec0ada2e9a4f5767b6 its not going to be backward ABI compatible with honister due to variable renaming. Signed-off-by: Khem Raj <raj.khem@gmail.com> 2021-08-03T17:21:25+00:00 Martin Jansa Martin.Jansa@gmail.com 2021-07-30T08:18:01+00:00 urn:sha1:17adfde3bdb533a228617859b2ce22da245dc7d5 This marks the layers as compatible with honister now they use the new override syntax. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> 2021-03-19T18:58:17+00:00 Khem Raj raj.khem@gmail.com 2021-03-19T18:32:38+00:00 urn:sha1:5daae70617cf1cff517c1d0ea37c8fe6e804d116 Signed-off-by: Khem Raj <raj.khem@gmail.com> 2020-11-04T20:43:55+00:00 Khem Raj raj.khem@gmail.com 2020-11-04T20:41:26+00:00 urn:sha1:8fbaa7e41cc30dcffc82447c780b456119541029 Thats codename for 3.3 Signed-off-by: Khem Raj <raj.khem@gmail.com> 2020-10-15T18:42:15+00:00 Khem Raj raj.khem@gmail.com 2020-10-15T16:19:27+00:00 urn:sha1:cd9eaf431863f03424343ad9acfad75a95c7dcd3 Remove older releases from COMPAT Signed-off-by: Khem Raj <raj.khem@gmail.com> 2020-08-31T23:57:06+00:00 Khem Raj raj.khem@gmail.com 2020-08-31T23:46:17+00:00 urn:sha1:52a070f02cd51a45df4238ff270a5ff87e58f0f5 openzone and rodent-icon-theme are allarch but recently gtk-icon-cache, since commit 31e3d34c8a9c3e8481aa837aa0bf52adf095fe62 [gtk-icon-cache.bbclass: add runtime dependency], it start depend on non-allarch packages gdk-pixbuf and gtk+3, which make it's signature changes when machine changed. Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Andreas Müller <schnitzeltony@gmail.com> 2020-03-20T14:44:29+00:00 Khem Raj raj.khem@gmail.com 2020-03-20T07:15:18+00:00 urn:sha1:46ae08202a52af4788372ba8c8e0ecefaa7eb301 Signed-off-by: Khem Raj <raj.khem@gmail.com>