mkimage-profiles/features.in/services/config.mk

use/services: sub/rootfs
	@$(call add_feature)
	@$(call xport,DEFAULT_SERVICES_ENABLE)
	@$(call xport,DEFAULT_SERVICES_DISABLE)
	@$(call xport,SERVICES_ENABLE)
	@$(call xport,SERVICES_DISABLE)
	@$(call xport,DEFAULT_SYSTEMD_SERVICES_ENABLE)
	@$(call xport,DEFAULT_SYSTEMD_SERVICES_DISABLE)
	@$(call xport,SYSTEMD_SERVICES_ENABLE)
	@$(call xport,SYSTEMD_SERVICES_DISABLE)
	@$(call xport,SYSTEMD_SERVICES_MASK)
	@$(call xport,SYSTEMD_SERVICES_UNMASK)
	@$(call xport,DEFAULT_SYSTEMD_USER_SERVICES_ENABLE)
	@$(call xport,DEFAULT_SYSTEMD_USER_SERVICES_DISABLE)
	@$(call xport,SYSTEMD_USER_SERVICES_ENABLE)
	@$(call xport,SYSTEMD_USER_SERVICES_DISABLE)

user/services/dbus-brocker: use/services
	@$(call add,DEFAULT_SERVICES_ENABLE,dbus-broker)
	@$(call add,DEFAULT_SYSTEMD_USER_SERVICES_ENABLE,dbus-broker)

use/services/lvm2-disable: use/services
	@$(call add,DEFAULT_SERVICES_DISABLE,lvm2-lvmetad)
	@$(call add,DEFAULT_SERVICES_DISABLE,lvm2-lvmpolld)
	@$(call add,DEFAULT_SERVICES_DISABLE,lvm2-monitor)
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/services: sub/rootfs`
			`@$(call add_feature)`
			`@$(call xport,DEFAULT_SERVICES_ENABLE)`
			`@$(call xport,DEFAULT_SERVICES_DISABLE)`
			`@$(call xport,SERVICES_ENABLE)`
			`@$(call xport,SERVICES_DISABLE)`
services: add defaults for SYSTEMD and SYSTEMD_USER services 2022-10-10 09:41:38 +03:00			`@$(call xport,DEFAULT_SYSTEMD_SERVICES_ENABLE)`
			`@$(call xport,DEFAULT_SYSTEMD_SERVICES_DISABLE)`
features/services: Add SYSTEMD_SERVICES_{ENABLE,DISABLE} Support systemd-spicific services, e.g. *.socket amd .service units. 2019-12-12 17:44:18 +03:00			`@$(call xport,SYSTEMD_SERVICES_ENABLE)`
			`@$(call xport,SYSTEMD_SERVICES_DISABLE)`
services: Add (un)mask systemd units Suggested-by: Anton Midyukov <antohami@altlinux.org> See: https://bugzilla.altlinux.org/47595 2023-10-06 17:48:36 +03:00			`@$(call xport,SYSTEMD_SERVICES_MASK)`
			`@$(call xport,SYSTEMD_SERVICES_UNMASK)`
services: add defaults for SYSTEMD and SYSTEMD_USER services 2022-10-10 09:41:38 +03:00			`@$(call xport,DEFAULT_SYSTEMD_USER_SERVICES_ENABLE)`
			`@$(call xport,DEFAULT_SYSTEMD_USER_SERVICES_DISABLE)`
services: add systemd-logind support 2022-09-30 07:39:35 +03:00			`@$(call xport,SYSTEMD_USER_SERVICES_ENABLE)`
			`@$(call xport,SYSTEMD_USER_SERVICES_DISABLE)`

services: add dbus-broker service (need systemd) 2023-07-13 20:46:16 +03:00			`user/services/dbus-brocker: use/services`
services: fix copypaste in use/services/dbus-broker 2023-08-17 10:12:38 +03:00			`@$(call add,DEFAULT_SERVICES_ENABLE,dbus-broker)`
services: add dbus-broker service (need systemd) 2023-07-13 20:46:16 +03:00			`@$(call add,DEFAULT_SYSTEMD_USER_SERVICES_ENABLE,dbus-broker)`
services: lvm2-* disable target These are creeping throughout m-p and aren't really needed by default as these should be enabled upon configuration; let's provide a single switch off point. 2017-08-02 21:14:42 +03:00
			`use/services/lvm2-disable: use/services`
			`@$(call add,DEFAULT_SERVICES_DISABLE,lvm2-lvmetad)`
			`@$(call add,DEFAULT_SERVICES_DISABLE,lvm2-lvmpolld)`
			`@$(call add,DEFAULT_SERVICES_DISABLE,lvm2-monitor)`