Specifying runtime package dependencies
The end results of most recipes are packages that are managed by the package manager. As we saw in the previous sections, it requires information about all those packages and how they relate to each other. For example, a package may depend on or conflict with another.
There are multiple package constraints that need to be expressed; however, those constraints are package format-specific, so BitBake has a specific metadata set used to abstract those package constraints.
Here is a list of the most commonly used runtime constraints:
RDEPENDS: This is the list of packages that are required to be installed along with the package that defines it.RPROVIDES: This is the list of symbolic names a package provides. By default, a package always includes the package name as a symbolic name. It can also include other symbolic names alternatively provided by that package.RCONFLICTS: This is the list of packages that are known to conflict with this package. Only one...
