mirror of
https://github.com/openembedded/meta-openembedded.git
synced 2026-06-16 18:40:03 +00:00
Robert Joslyn
cef2d1429b
Upstream renamed the branch to "main", update SRC_URI. Refresh pkg-config patch. Update PACKAGECONFIG options. The linux-affinity option was renamed to affinity. Add a packageconfig conflict between affinity and hwloc, since these are mutually exclusive. The setuid option was removed by upstream, and a capabilities option added. The sensors option switched from --with/--without to --enable/--disable. Reorder the option to match the order used in the configure script to make future updates easier. License-Update: The previous license contained an exception for the Portable Linux Processor Affinity (PLPA) project. This exception has been removed, so the project uses an unmodified GPLv2 license. Minor formatting and whitespace changes were also made to match the license text as published by the FSF. Commit making change: https://github.com/htop-dev/htop/commit/088dc5b9a7a5352ee7fdf85f3aff1368958634eb Signed-off-by: Robert Joslyn <robert.joslyn@redrectangle.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>
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 <remote>' 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>