mkimage-profiles/lib/help.mk

# this makefile holds the most helpful bits for the toplevel one

define help_body
if [ -t 1 ]; then \
	echo '** available $(1) targets:'; \
	columnize $(2); \
else \
	printf '%s\n' $(2); \
fi
endef

help = $(and $(2),$(help_body))

help/distro:
	@$(call help,distribution,$(sort $(DISTROS:distro/%=%)))

help/ve:
	@[ -n "$(SPACE)" ] && echo; \
	$(call help,virtual environment,$(sort $(VES)))

help/vm:
	@[ -n "$(SPACE)" ] && echo; \
	$(call help,virtual machine,$(sort $(VMS)))

help: SPACE = 1
help: help/distro help/ve help/vm; @:
main.mk: factored out help targets These are better off in their own lib/help.mk 2012-03-19 15:23:58 +04:00			`# this makefile holds the most helpful bits for the toplevel one`

initial frontend support 2012-05-12 17:22:15 +04:00			`define help_body`
help.mk, clean.mk: drop __frontend for tty test The __frontend variable was introduced to address the needs of alterator-mkimage module: list the images available in one column, purge the builddir. Looks like we should consider other cases with redirected stdout (cron builds, piped calls, etc) like fundamentally non-interactive and behave the same. So commit 3a8af6b55d888d25c1d97561ed2ecf37ff28ad71's description is wrong now; the current cleanup rules are: - if CLEAN=0 or DEBUG>1, don't do it; - if CHECK or REPORT is set, don't do it; - otherwise if at least one of the following conditions is true: + there's more than one target being built in a row; + stdout was redirected (cronjob, alterator-mkimage...); + metaprofile directory is read-only ...then do a distclean. If that doesn't suit your needs, describe the particular situation please. Thanks cas@ for wondering aloud whether greppable output is unsupported with `make help'. 2015-04-02 16:13:07 +03:00			`if [ -t 1 ]; then \`
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration 2012-06-18 22:00:32 +04:00			`echo '** available $(1) targets:'; \`
help.mk, clean.mk: drop __frontend for tty test The __frontend variable was introduced to address the needs of alterator-mkimage module: list the images available in one column, purge the builddir. Looks like we should consider other cases with redirected stdout (cron builds, piped calls, etc) like fundamentally non-interactive and behave the same. So commit 3a8af6b55d888d25c1d97561ed2ecf37ff28ad71's description is wrong now; the current cleanup rules are: - if CLEAN=0 or DEBUG>1, don't do it; - if CHECK or REPORT is set, don't do it; - otherwise if at least one of the following conditions is true: + there's more than one target being built in a row; + stdout was redirected (cronjob, alterator-mkimage...); + metaprofile directory is read-only ...then do a distclean. If that doesn't suit your needs, describe the particular situation please. Thanks cas@ for wondering aloud whether greppable output is unsupported with `make help'. 2015-04-02 16:13:07 +03:00			`columnize $(2); \`
			`else \`
			`printf '%s\n' $(2); \`
			`fi`
initial frontend support 2012-05-12 17:22:15 +04:00			`endef`

			`help = $(and $(2),$(help_body))`

main.mk: factored out help targets These are better off in their own lib/help.mk 2012-03-19 15:23:58 +04:00			`help/distro:`
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration 2012-06-18 22:00:32 +04:00			`@$(call help,distribution,$(sort $(DISTROS:distro/%=%)))`
main.mk: factored out help targets These are better off in their own lib/help.mk 2012-03-19 15:23:58 +04:00
			`help/ve:`
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration 2012-06-18 22:00:32 +04:00			`@[ -n "$(SPACE)" ] && echo; \`
			`$(call help,virtual environment,$(sort $(VES)))`
main.mk: factored out help targets These are better off in their own lib/help.mk 2012-03-19 15:23:58 +04:00
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration 2012-06-18 22:00:32 +04:00			`help/vm:`
			`@[ -n "$(SPACE)" ] && echo; \`
			`$(call help,virtual machine,$(sort $(VMS)))`

			`help: SPACE = 1`
			`help: help/distro help/ve help/vm; @:`