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

use/repo:
	@$(call add_feature)
	@$(call add,STAGE1_PACKAGES,gnupg)
	@$(call xport,ROOTFS_MAIN)

use/repo/main:: sub/main use/repo; @:

ifeq (vm,$(IMAGE_CLASS))
use/repo/main::
	@$(call set,ROOTFS_MAIN,1)
	@$(call add,THE_PACKAGES,apt-repo-tools)
endif

use/repo/addon: use/repo/main
	@$(call set,MAIN_SUFFIX,addon)
initial repo feature We've got some parts of it in build-distro feature, and some went to dev feature for no real reason. But a bare installer might go without package base, and LiveCDs other than live-builder might find local repository useful given aufs2 root overlay. Now the overall scheme is more straightforward: - a distro: + asks that a package repo be included + cares to further add the packages to it - a repo feature: + pulls in sub/main for it to happen + provides genbasedir script to create repo metadata + supplements live feature with repo configuration 2011-11-14 18:24:07 +04:00			`use/repo:`
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)`
repo: generate RPM-GPG-KEY as well Just a hook to export alt-gpgkeys pubring data. 2011-12-01 21:44:41 +04:00			`@$(call add,STAGE1_PACKAGES,gnupg)`
repo: use/repo/main for vm targets use/repo/main for vm targets will now create and enable the main repository in /ALTLinux on rootfs. 2020-10-28 20:02:00 +03:00			`@$(call xport,ROOTFS_MAIN)`
initial repo feature We've got some parts of it in build-distro feature, and some went to dev feature for no real reason. But a bare installer might go without package base, and LiveCDs other than live-builder might find local repository useful given aufs2 root overlay. Now the overall scheme is more straightforward: - a distro: + asks that a package repo be included + cares to further add the packages to it - a repo feature: + pulls in sub/main for it to happen + provides genbasedir script to create repo metadata + supplements live feature with repo configuration 2011-11-14 18:24:07 +04:00
repo: use/repo/main for vm targets use/repo/main for vm targets will now create and enable the main repository in /ALTLinux on rootfs. 2020-10-28 20:02:00 +03:00			`use/repo/main:: sub/main use/repo; @:`

			`ifeq (vm,$(IMAGE_CLASS))`
			`use/repo/main::`
			`@$(call set,ROOTFS_MAIN,1)`
			`@$(call add,THE_PACKAGES,apt-repo-tools)`
			`endif`
main, repo: introduced suffix support This is to make building addon images possible; those carrying packages but lacking any stage2. 2018-07-25 17:20:30 +03:00
			`use/repo/addon: use/repo/main`
			`@$(call set,MAIN_SUFFIX,addon)`