aboutsummaryrefslogtreecommitdiff
path: root/PACKAGE.md
diff options
context:
space:
mode:
authorStefano Stabellini2020-09-14 17:41:08 -0700
committerStefano Stabellini2020-09-22 11:42:58 -0700
commit3956b70f583490df9ed0d3d16cc89eb5c1af1001 (patch)
tree31a9dce6a3b2f7ccd79e7ecd2f5cc302f0a2fdf0 /PACKAGE.md
parent6bfed7743ac709a64e22e3832d353eed7c39ff78 (diff)
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 <stefano.stabellini@xilinx.com> Reviewed-by: Brian Woods <brian.woods@xilinx.com>
Diffstat (limited to 'PACKAGE.md')
-rw-r--r--PACKAGE.md24
1 files changed, 0 insertions, 24 deletions
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-<name>/
-```
-
-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.