diskimage-builder

History

Monty Taylor 98d008c6af Rework package-installs to collapse on build host Instead of doing the work in the image of parsing through the element's package-install declarations, we can squash it on hostside, where we have both YAML and JSON available to us, and then emit a single pre-processed file into the target to be used later. Change-Id: I3f182aa3aae0a79b2f3ea4e66c1878ad12878b0a		2014-12-11 00:05:32 -08:00
..
bin	Rework package-installs to collapse on build host	2014-12-11 00:05:32 -08:00
extra-data.d	Rework package-installs to collapse on build host	2014-12-11 00:05:32 -08:00
install.d	Rework package-installs to collapse on build host	2014-12-11 00:05:32 -08:00
post-install.d	Rework package-installs to collapse on build host	2014-12-11 00:05:32 -08:00
pre-install.d	Rework package-installs to collapse on build host	2014-12-11 00:05:32 -08:00
element-deps	package-installs for pre-install.d/post-install.d	2014-08-14 21:18:19 -04:00
README.rst	Add new package-installs system	2014-12-01 21:29:47 -08:00

README.rst

The package-installs element allows for a declarative method of installing and
uninstalling packages for an image build. This is done by creating a
package-installs.yaml or package-installs.json file in the element directory.


example package-installs.yaml:
libxml2:
grub2:
  phase: pre-install.d
networkmanager:
  uninstall: True

example package-installs.json:
{
  "libxml2": null,
  "grub2": {"phase": "pre-install.d"},
  "networkmanager": {"uninstall": true}
}


Setting phase or uninstall properties for a package overrides the following
default values:

phase: install.d
uninstall: False


DEPRECATED: Adding a file under your elements pre-install.d, install.d, or
post-install.d directories called package-installs-<element-name> will cause
the list of packages in that file to be installed at the beginning of the
respective phase.  If the package name in the file starts with a "-", then
that package will be removed at the end of the install.d phase.