mkimage-profiles/features.in/cleanup/install2/image-scripts.d/90cleanup-pkgs

#!/bin/sh -efu
### create a postinstall script to drop temporarily needed packages

if [ -n "$GLOBAL_VERBOSE" ]; then
	echo "** GLOBAL_CLEANUP_PACKAGES: $GLOBAL_CLEANUP_PACKAGES"
fi >&2

SCRIPT="/usr/share/install2/postinstall.d/01-remove-pkgs"
cat > "$SCRIPT" << EOF
#!/bin/sh -efu

. install2-init-functions

# don't override the script start message on the same line
echo "removing $GLOBAL_CLEANUP_PACKAGES"

# remove extra packages from installed system
list="\$(exec_chroot rpmquery -a --qf='%{NAME}\\n' $GLOBAL_CLEANUP_PACKAGES)"
[ -z "\$list" ] || exec_chroot apt-get remove -f -y  -- \$list
EOF
chmod +x "$SCRIPT"
initial features.in/cleanup This is a sort of anti-feature which removes and not builds; still with mkimage-profiles' approach we can at least build up the removal procedures as well. It's what triggered the tagged scripts, BTW. 2011-09-13 20:39:31 +04:00			`#!/bin/sh -efu`
tagged scripts breakage partially fixed It appears that features.in/Makefile functioned a bit differently by now than was described back then: after loops and pushds got rearranged for robustness, it stopped to pick up a cleanup feature tagged script. That particular script is now better de-tagged and simply placed as a script to be merged into install2 subprofile. The tagged scripts still require a bit more comprehension to understand the use cases (e.g., do we need per-subprofile tagged script subdirs or just a toplevel one should be looked at, with script names telling where to put them). README used to mix up subprofiles and features; fixed. 2011-11-14 22:48:56 +04:00			`### create a postinstall script to drop temporarily needed packages`
initial features.in/cleanup This is a sort of anti-feature which removes and not builds; still with mkimage-profiles' approach we can at least build up the removal procedures as well. It's what triggered the tagged scripts, BTW. 2011-09-13 20:39:31 +04:00
			`if [ -n "$GLOBAL_VERBOSE" ]; then`
			`echo "** GLOBAL_CLEANUP_PACKAGES: $GLOBAL_CLEANUP_PACKAGES"`
			`fi >&2`

tagged scripts breakage partially fixed It appears that features.in/Makefile functioned a bit differently by now than was described back then: after loops and pushds got rearranged for robustness, it stopped to pick up a cleanup feature tagged script. That particular script is now better de-tagged and simply placed as a script to be merged into install2 subprofile. The tagged scripts still require a bit more comprehension to understand the use cases (e.g., do we need per-subprofile tagged script subdirs or just a toplevel one should be looked at, with script names telling where to put them). README used to mix up subprofiles and features; fixed. 2011-11-14 22:48:56 +04:00			`SCRIPT="/usr/share/install2/postinstall.d/01-remove-pkgs"`
initial features.in/cleanup This is a sort of anti-feature which removes and not builds; still with mkimage-profiles' approach we can at least build up the removal procedures as well. It's what triggered the tagged scripts, BTW. 2011-09-13 20:39:31 +04:00			`cat > "$SCRIPT" << EOF`
			`#!/bin/sh -efu`

			`. install2-init-functions`

			`# don't override the script start message on the same line`
			`echo "removing $GLOBAL_CLEANUP_PACKAGES"`

			`# remove extra packages from installed system`
			`list="\$(exec_chroot rpmquery -a --qf='%{NAME}\\n' $GLOBAL_CLEANUP_PACKAGES)"`
			`[ -z "\$list" ] \|\| exec_chroot apt-get remove -f -y -- \$list`
			`EOF`
			`chmod +x "$SCRIPT"`