meta-openembedded/meta-oe
Peter Marko c4a6fc8b40
grpc: add licenses from third party components
There are 9 (out of 24) third party components used for build.
Add their licenses.

SUB third_party/abseil-cpp            .. not used (unbundled)
    third_party/address_sorting       .. USED
SUB third_party/benchmark             .. not used (testing)
SUB third_party/bloaty                .. not used (testing)
SUB third_party/boringssl-with-bazel  .. not used (unbundled; openssl)
    third_party/cares                 .. not used (unbundled)
SUB third_party/envoy-api             .. USED
SUB third_party/googleapis            .. USED
SUB third_party/googletest            .. not used (testing)
    third_party/objective_c           .. not used (build helpers)
SUB third_party/opencensus-proto      .. USED
SUB third_party/opentelemetry         .. not used (gRPC_BUILD_GRPCPP_OTEL_PLUGIN)
SUB third_party/opentelemetry-cpp     .. not used (gRPC_BUILD_GRPCPP_OTEL_PLUGIN)
SUB third_party/protobuf              .. not used (unbundled)
SUB third_party/protoc-gen-validate   .. USED
    third_party/py                    .. not used (build helpers)
    third_party/rake-compiler-dock    .. not used (build helpers)
SUB third_party/re2                   .. not used (unbundled)
    third_party/toolchains            .. not used (build helpers)
    third_party/upb                   .. USED
    third_party/utf8_range            .. USED
SUB third_party/xds                   .. USED
    third_party/xxhash                .. USED
SUB third_party/zlib                  .. not used (unbundled)

* address_sorting - BSD-3-CLAUSE (already in main license)
  https://github.com/grpc/grpc/blob/master/third_party/address_sorting/LICENSE
* envoy-api - Apache-2.0 (already in main license)
  4de3c74cf2/LICENSE
* googleapis - Apache-2.0 (already in main license)
  fe8ba054ad/LICENSE
* opencensus-proto - Apache-2.0 (already in main license)
  4aa53e15cb/LICENSE
* protoc-gen-validate - Apache-2.0 (already in main license)
  32c2415389/LICENSE
* upb - BSD-3-Clause (already present in main LICENSE)
  there is a note in all files
* utf8_range - MIT
  https://github.com/grpc/grpc/blob/master/third_party/utf8_range/LICENSE
* xds - Apache-2.0 (already in main license)
  3a472e5248/LICENSE
* xxhash - BSD-2-Clause
  https://github.com/grpc/grpc/blob/master/third_party/xxhash/LICENSE

License-Update: added missing licenses

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-02-08 20:43:46 -08:00
..
classes capnproto: remove binaries from target-build, add bbclass 2025-02-03 11:25:22 -08:00
conf spdm-utils: Initial support for spdm-utils 2025-02-04 20:25:51 -08:00
dynamic-layers spdm-utils: Initial support for spdm-utils 2025-02-04 20:25:51 -08:00
files
lib/oeqa/selftest/cases
licenses openldap: make license match spdx identifier 2025-02-04 20:25:51 -08:00
recipes-benchmark recipes: Fix variable assignment whitespace 2025-01-31 10:34:03 -08:00
recipes-bsp nvme-cli: Fix musl build erros for v2.11 2024-11-21 21:42:36 -08:00
recipes-connectivity iwd: update 3.2 -> 3.3 2025-01-24 18:20:05 -08:00
recipes-core plymouth: remove extra kernel parameter 2025-01-30 12:30:08 -08:00
recipes-crypto botan: update 3.5.0 -> 3.6.1 2025-01-03 10:17:22 -08:00
recipes-dbs mariadb: Upgrade to 11.4.4 2025-01-14 20:14:27 -08:00
recipes-devtools grpc: add licenses from third party components 2025-02-08 20:43:46 -08:00
recipes-extended valkey: Upgrade 8.0.1 -> 8.0.2 2025-02-07 08:37:18 -08:00
recipes-gnome malcontent: set pam module path to ${base_libdir}/security 2025-01-06 07:22:29 -08:00
recipes-graphics gphoto: Fix regex to remove --sysroot from CC in config.h 2025-02-06 21:51:34 -08:00
recipes-kernel crash-cross-canadian: Update to match OE-Core virtual provider changes 2025-01-25 09:36:49 -08:00
recipes-multimedia audiofile: mark CVE-2020-18781 as patched 2025-01-17 16:39:40 -08:00
recipes-navigation gpsd: condition the runtime dependence of pyserial on the pygps 2024-09-27 06:18:13 -07:00
recipes-networking/cyrus-sasl Drop unnecessary SRC_URI md5sum from the recipes in meta-oe. 2024-11-05 19:19:22 -08:00
recipes-printing cups-filters: include UPSTREAM_CHECK_URI to fix UNKNOWN_BROKEN status 2024-07-24 08:56:30 -07:00
recipes-security spectre-meltdown-checker: fix script name 2025-02-06 12:25:21 -08:00
recipes-shells dash: set CVE_PRODUCT 2024-12-10 13:43:54 -08:00
recipes-support libatasmart: fix SRC_URI protocol 2025-02-05 13:56:33 -08:00
recipes-test syzkaller: network in compile is not needed 2024-12-10 08:39:04 -08:00
COPYING.MIT
README.md README.md: Hint at "git request-pull" 2024-09-14 08:43:55 -07:00
SECURITY.md meta: Add SECURITY.md file to all layers 2024-11-23 09:00:14 -08: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.

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