mkimage-profiles/features.in/build-ve/config.mk

# hooked from lib/sugar.mk
use/build-ve: sub/rootfs@/
	@$(call add_feature)
documentation: use paths relative to toplevel dir This change is done to reduce ambiguity in some cases; the previous intention has been to ease navigation when staying in a particular directory, now it's been changed in favour of convenient toplevel `git grep' in fact. Both variants have their pros and cons, I just find myself leaning to this one by now hence the commit. Feel free to provide constructive criticism :) Some path-related bitrot has also been fixed while at that. 2014-03-05 18:09:56 +04:00			`# hooked from lib/sugar.mk`
initial rootfs subprofile and services feature This subprofile is akin to THE_* variables family: the configuration bits and script hooks sitting there influence whatever chroot is declared to be the user facing one in the end, whether it comes from vm image or live subprofile. The services feature ought to be a changeset of its own which would be based on rootfs and become the base for ve/vm changes but I chose to just do it atomically; some pre-existing duplicates are pruned now. 2013-05-28 12:51:36 +04:00			`use/build-ve: sub/rootfs@/`
introduced add_feature function 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... 2011-11-16 19:58:42 +04:00			`@$(call add_feature)`