9cedefdba9
The features might get copy-pasted (or even copied-and-pruned) when initialized; there's an unneccessary duplication of the function name in the line adding it to FEATURES list, thus prone to being forgotten and causing some havoc later on. It was wrong in the first place but tackling this with some double-colon rules ran into terminality issues, and further tortures were considered unneccessary. The current solution isn't perfect (no completely transparent function name registration upon corresponding target being called) but at least it is an improvement...
20 lines
702 B
Makefile
20 lines
702 B
Makefile
use/cleanup:
|
|
@$(call add_feature)
|
|
|
|
use/cleanup/installer: use/cleanup
|
|
@$(call add,CLEANUP_PACKAGES,'installer-*')
|
|
|
|
use/cleanup/x11: use/cleanup
|
|
@$(call add,CLEANUP_PACKAGES,libSM libXext libXmu libXi)
|
|
|
|
# as some alterator modules are installed into stage3 (the destination
|
|
# root filesystem) to perform actions like bootloader setup, we might
|
|
# have to remove them (contrary to the usual build-up)...
|
|
use/cleanup/alterator: use/cleanup
|
|
@$(call add,CLEANUP_PACKAGES,'alterator*' rpm-macros-alterator)
|
|
@$(call add,CLEANUP_PACKAGES,'guile*' libvhttpd)
|
|
|
|
# for lightweight server distros
|
|
use/cleanup/x11-alterator: use/cleanup/x11 use/cleanup/alterator
|
|
@$(call add,CLEANUP_PACKAGES,libmng qt4-common)
|