meta-openembedded/meta-oe
Martin Jansa be8c765c7c *.patch: add Upstream-Status to all patches
There is new patch-status QA check in oe-core:
https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac67157762a53259089ea8a

This is temporary work around just to hide _many_ warnings from
optional patch-status (if you add it to WARN_QA).

This just added
Upstream-Status: Pending
everywhere without actually investigating what's the proper status.

This is just to hide current QA warnings and to catch new .patch files being
added without Upstream-Status, but the number of Pending patches is now terrible:

5 (26%) 	meta-xfce
6 (50%) 	meta-perl
15 (42%)        meta-webserver
21 (36%)        meta-gnome
25 (57%)        meta-filesystems
26 (43%)        meta-initramfs
45 (45%)        meta-python
47 (55%)        meta-multimedia
312 (63%)       meta-networking
756 (61%)       meta-oe

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2023-06-21 09:15:20 -07:00
..
classes gitpkgv: Fix python deprecation warning 2023-05-03 16:26:17 -07:00
conf meta-oe: add pahole to NON_MULTILIB_RECIPES 2023-06-08 19:34:34 -07:00
dynamic-layers lirc: Define SH_PATH=/bin/sh 2023-05-19 10:12:51 -07:00
lib/oeqa/selftest/cases syzkaller: add recipe and selftest for syzkaller fuzzing 2022-10-21 09:57:59 -07:00
licenses mimic: Use special rateconv.c license 2022-04-30 09:52:15 -07:00
recipes-benchmark *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-bsp *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-connectivity *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-core *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-crypto libtomcrypt: pass LIBPATH to fix installed-vs-shipped with multilib 2023-05-04 06:47:00 -07:00
recipes-dbs *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-devtools *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-extended *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-gnome adw-gtk3: upgrade 4.7 -> 4.8 2023-06-19 10:24:49 -07:00
recipes-graphics *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-kernel *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-multimedia *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-navigation *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-networking/cyrus-sasl *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-printing *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-security *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-shells *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-support *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
recipes-test *.patch: add Upstream-Status to all patches 2023-06-21 09:15:20 -07:00
COPYING.MIT
README.md layers: Move READMEs to markdown format 2023-06-17 08:30:01 -07:00

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.

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