d65678678e
Move dib-run-parts from dib-utils into diskimage-builder directly. For calling outside the chroot, we provide a standard entry-point script. However, as noted in the warning comment, the underlying script is still copied directly into the chroot by the dib-run-parts element. I believe this to be the KISS approach. This removes the dependency on dib-utils. We have discussed this previously and nobody seemed to think retiring dib-utils was going to be an issue. This also updates the documentation to not mention dib-utils, or using disk-image-create via $PATH setup, but rather gives instructions on installing from pip with a virtualenv. Change-Id: Ic1e22ba498d2c368da7d72e2e2b70ff34324feb8 |
||
---|---|---|
.. | ||
1.16.0-updates-bad91fc0b36c1755.yaml | ||
1.17.0-ef744f36d277dba4.yaml | ||
1.18.0-4433d3076627f10d.yaml | ||
1.18.1-ceeb514708dcb731.yaml | ||
block-device-handling-279cddba8a859718.yaml | ||
element-info-entry-point-448bf622be6061a0.yaml | ||
element-override-ccda78c24ab4a4ff.yaml | ||
element-vars-c6bf2e6795002f01.yaml | ||
opensuse-minimal-45267f5be1112c22.yaml | ||
package-install-arch-38bb5a6e61794fa5.yaml | ||
remove-dib-utils-37f70dfad54900a0.yaml | ||
runtime-ssh-host-keys-7a2fc873cc90d33e.yaml | ||
start-using-reno-446b3d52a467a273.yaml |