From 3956b70f583490df9ed0d3d16cc89eb5c1af1001 Mon Sep 17 00:00:00 2001 From: Stefano Stabellini Date: Mon, 14 Sep 2020 17:41:08 -0700 Subject: Removed unused container-based usage Initially ImageBuilder was meant to be mainly invoked from a container but in practice ImageBuilder's scripts have been called directly. Remove the old documentation and Dockerfile. Signed-off-by: Stefano Stabellini Reviewed-by: Brian Woods --- PACKAGE.md | 24 ------------------------ 1 file changed, 24 deletions(-) delete mode 100644 PACKAGE.md (limited to 'PACKAGE.md') diff --git a/PACKAGE.md b/PACKAGE.md deleted file mode 100644 index 9d37e1c..0000000 --- a/PACKAGE.md +++ /dev/null @@ -1,24 +0,0 @@ -# A container package - -Imagebuilder takes multiple `package` containers as input and produces a -runnable u-boot script or a runnable disk image as output. This document -describes the package format. - -A package is a container containing all the relevant binaries for a -given component under the following path: - -``` -/home/builder/output-/ -``` - -For instance, for DomUs a package containes the kernel, rootfs, -additional configuration. As an example, zynqmp-dom1-package contains -the following files: - -``` -/home/builder/output-zynqmp-dom1/Image-domU -/home/builder/output-zynqmp-dom1/domU-ramdisk.cpio -/home/builder/output-zynqmp-dom1/passthrough-example-part.dtb -``` - -Which are the kernel, ramdisk, passthrough configuration respectively. -- cgit v1.2.3