mirror of
https://github.com/thead-yocto-mirror/meta-openembedded
synced 2026-08-22 17:07:41 +02:00
c75d215d9c
* TUNE_PKGARCH cannot RRECOMMEND MACHINE specific kernel-modules * without virtual/kernel dependency (which isn't really build time dependency) the QA check won't traverse the dependencies correctly and shows following errors: ERROR: QA Issue: freediameter rdepends on kernel-module-ipip, but it isn't a build dependency? [build-deps] ERROR: QA Issue: freediameter rdepends on kernel-module-sctp, but it isn't a build dependency? [build-deps] ERROR: QA Issue: freediameter rdepends on kernel-module-tipc, but it isn't a build dependency? [build-deps] ERROR: QA Issue: freediameter rdepends on kernel-module-udp-tunnel, but it isn't a build dependency? [build-deps] * also change kernel-module dependencies from RDEPENDS to RRECOMMENDS because the kernel config might include these directly and then freediameter shouldn't fail to install Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
meta-networking
===============
This layer is intended to be a central point for networking-related
packages and configuration. It should be useful directly on top of
oe-core and compliments meta-openembedded. It should be primarily useful
to the following groups:
- Anyone building a small networking device (eg. a home router /
bridge / switch).
- Anyone wanting to add network services to their device (eg.
anything that might benefit from a small ftp/tftp server)
Dependencies
------------
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git
branch: master
revision: HEAD
For some recipes, the meta-oe layer is required:
URI: git://github.com/openembedded/meta-openembedded.git
subdirectory: meta-oe
branch: master
revision: HEAD
URI: git://github.com/openembedded/meta-openembedded.git
subdirectory: meta-python
branch: master
revision: HEAD
Maintenance
-----------
Please see the MAINTAINERS file for information on contacting the
maintainers of this layer, as well as instructions for submitting patches.