meta-openembedded/meta-oe
Yoann Congal bf400cd73f
reproducibility: move known non-repro list to layer.conf
The current include file that stores the known non-reproducible packages
is layer dependent and that forces the user of the layers to maintain
the list of the files (for example, see AB config[0]).

By moving the exclude list to each layer.conf and extending the common
OEQA_REPRODUCIBLE_EXCLUDED_PACKAGES variable, the known non-reproducible
packages will be automatically excluded for each layer used in the
reproducibility test without any special knowledge in the test
environment.

NB: the empty list for meta-initramfs was just removed not moved.

[0]: https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.json?id=7d8933e75bdf7fb821a25617cb2dcabf1f3f8700#n322

Suggested-by: Quentin Schulz <quentin.schulz@cherry.de>
Co-Developed-by: Guillaume Swaenepoel <guillaume.swaenepoel@smile.fr>
Signed-off-by: Guillaume Swaenepoel <guillaume.swaenepoel@smile.fr>
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-06-20 10:34:11 -07:00
..
classes check-version-mismatch.bbclass: use oe.qemu and add QEMU_OPTIONS settings 2025-05-29 22:28:02 -07:00
conf reproducibility: move known non-repro list to layer.conf 2025-06-20 10:34:11 -07:00
dynamic-layers thingsboard-gateway: upgrade 3.7.2 -> 3.7.4 2025-05-21 07:38:27 -07:00
files
lib/oeqa/selftest/cases
licenses
recipes-benchmark libhugetlbfs: remove obsolete python/perl dependencies 2025-06-12 06:34:20 -07:00
recipes-bsp dediprog-flasher: enable native builds 2025-05-14 15:51:46 -07:00
recipes-connectivity thrift: upgrade 0.21.0 -> 0.22.0 2025-06-09 21:24:17 -07:00
recipes-core uutils-coreutils: upgrade 0.0.30 -> 0.1.0 2025-05-27 10:33:01 -07:00
recipes-crypto
recipes-dbs postgresql: upgrade 17.4 -> 17.5 2025-05-21 07:38:25 -07:00
recipes-devtools abseil-cpp: upgrade 20250127.1 -> 20250512.0 2025-06-19 08:57:20 -07:00
recipes-extended dialog: fix /usr/bin/dialog not found for multilib 2025-06-12 06:34:19 -07:00
recipes-gnome
recipes-graphics directfb: remove sysfsutils DEPENDS 2025-06-12 06:34:20 -07:00
recipes-kernel crash: fix reproducibility 2025-05-27 10:33:01 -07:00
recipes-multimedia libvpx: upgrade 1.15.1 -> 1.15.2 2025-06-09 21:24:10 -07:00
recipes-navigation
recipes-networking/cyrus-sasl
recipes-printing qpdf: upgrade 12.1.0 -> 12.2.0 2025-05-21 07:38:26 -07:00
recipes-security audit: upgrade 4.0.4 -> 4.0.5 2025-06-09 21:24:07 -07:00
recipes-shells
recipes-support libsimplelog: v1.0.7 -> v1.0.8 2025-06-20 10:34:11 -07:00
recipes-test bats: upgrade 1.11.1 -> 1.12.0 2025-06-09 21:24:08 -07:00
COPYING.MIT
README.md
SECURITY.md

meta-oe

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git branch: master

luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below

pacman -S lib32-gcc-libs lib32-glibc

Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'

You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.

Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

layer maintainer: Khem Raj raj.khem@gmail.com