![]() These are a set of dependencies required to build and run docker and docker-registry which had previously existed in meta-cloud-services. By moving these from meta-cloud-services to meta-virtualization we can build and use docker without needing to include meta-cloud-services. Since meta-cloud-services depends on meta-virtualization these recipes will still be available for use with packages/images in meta-cloud-services. There is a concern that meta-cloud-services contains many python packages as there exists tight dependency for specific package versions, this move does not prevent this tight binding from continuing using various mechanisms made available to layers. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Amy Fong <amy.fong@windriver.com> |
||
---|---|---|
conf | ||
docs | ||
files/custom-licenses | ||
recipes-containers | ||
recipes-core | ||
recipes-devtools | ||
recipes-extended | ||
recipes-kernel/linux | ||
recipes-networking/openvswitch | ||
.gitignore | ||
COPYING.MIT | ||
README |
meta-virtualization
This layer provides support for building Xen, KVM, Libvirt, and associated packages necessary for constructing OE-based virtualized solutions.
Dependencies
This layer depends on:
URI: git://github.com/openembedded/oe-core.git branch: master revision: HEAD prio: default
URI: git://github.com/openembedded/meta-oe.git branch: master revision: HEAD layers: meta-oe meta-networking meta-filesystems
BBFILE_PRIORITY_openembedded-layer = "4"
Required for Xen XSM policy: URI: git://git.yoctoproject.org/meta-selinux branch: master revision: HEAD prio: default
Maintenance
Send pull requests, patches, comments or questions to meta-virtualization@yoctoproject.org
Maintainers: Raymond Danks ray.danks@se-eng.com Bruce Ashfield bruce.ashfield@gmail.com
When sending single patches, please using something like: 'git send-email -1 --to meta-virtualization@yoctoproject.org --subject-prefix=meta-virtualization][PATCH'
License
All metadata is MIT licensed unless otherwise stated. Source code included in tree for individual recipes is under the LICENSE stated in each recipe (.bb file) unless otherwise stated.