mkimage-profiles/image.in/functions.mk

# globals
PKGDIR := $(GLOBAL_BUILDDIR)/pkg

# duplicated from metaprofile makefiles for the sake of "local" builds
ARCH ?= $(shell arch | sed 's/i686/i586/; s/armv.*/arm/; s/ppc.*/ppc/')
DATE ?= $(shell date +%Y%m%d)

# prefix pkglist name with its directory to form a path (relative/absolute)
rlist = $(1:%=lists/%)
list  = $(addprefix $(PKGDIR)/,$(call rlist,$(1)))

# prefix/suffix group name to form a path (relative/absolute)
rgroup = $(1:%=groups/%.directory)
group  = $(addprefix $(PKGDIR)/,$(call rgroup,$(1)))

# map first argument (a function) onto second one (an argument list)
map = $(foreach a,$(2),$(call $(1),$(a)))

# kernel package list generation; see also #24669
NULL :=
SPACE := $(NULL) # the officially documented way of getting a space

list2re = $(subst $(SPACE),|,$(strip $(1)))

# args: KFLAVOURS, KMODULES
# NB: $(2) could be empty
kpackages = $(and $(1), \
	^kernel-(image|modules-($(call list2re,$(2))))-($(call list2re,$(1)))$$)

# arg: branding subpackages
branding = $(and $(1),^branding-$(BRANDING)-($(call list2re,$(1)))$$)
official {distro,ve}/* support This is quite a large-scale change since mkimage-profiles got used to baking distributions over the last year, and virtual environments are quite different, so e.g. image.in/Makefile had to be split in two with the main part of it moved into features.in/iso/lib/. Short overview: - features.in/Makefile: lib/ support (supporting VE images requires dynamic modifications to image.in/Makefile before starting the build; the most natural way to achieve that seems to use features mechanism along with makefile include dir) - packaging format related part moved into features.in/pack (should be better prepared for diversity either) - features.in/iso renamed to features.in/build-distro - features.in/ve renamed to features.in/build-ve + NB: these could not be merged as e.g. features.in/build due to completely different script hooks - lib/image.mk renamed to lib/build.mk - image, config, log postprocessing moved downstream - added a sort of a topping in the form of lib/sugar.mk - assorted style fixups (like ifeq usage) - clean.mk: reliability fix (the problem was observed by Oleg Ivanov and me too but finally it did get the attention quantum) - reviewed, updated and extended docs + QUICKSTART: should be[come] a step-by-step guide (thanks Leo-sp50 for prodiving feedback) 2011-10-06 12:46:31 +04:00			`# globals`
			`PKGDIR := $(GLOBAL_BUILDDIR)/pkg`
image.in/functions.mk: added ARCH dup If the build is (re-)run withing generated profile directory, the makefiles no longer have ARCH passed by upstream -- the upstream might be unreachable at that point indeed. This is unfortunate but we should cope with that. NB: might be revisited when architecture-specific packagelists emerge since currently there's no difference in package lists so we can just re-run the build for a different architecture but this might change... 2011-10-21 20:14:02 +04:00
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually... 2011-12-30 14:46:58 +04:00			`# duplicated from metaprofile makefiles for the sake of "local" builds`
initial PowerPC support As it happens, adding another architecture required almost no changes; native 32-bit ppc build took only ARCH and a repo, qemu-ppc one still has problems (/.host/entry hangs while unpacking setup for fakedata). Proof of concept on a QS22: $ make ve/bare.tar.gz ARCH: ppc /bin/sh: rpmvercmp: command not found 21:41:01 cleaning up 21:41:03 initializing BUILDDIR: build/ 21:41:03 preparing distro config 21:41:05 starting image build (coffee time) 21:42:48 done (1:42) image: $TMP/out/bare-20120716-ppc.tar.gz [21M] 2012-07-16 22:10:54 +04:00			`ARCH ?= $(shell arch \| sed 's/i686/i586/; s/armv./arm/; s/ppc./ppc/')`
official {distro,ve}/* support This is quite a large-scale change since mkimage-profiles got used to baking distributions over the last year, and virtual environments are quite different, so e.g. image.in/Makefile had to be split in two with the main part of it moved into features.in/iso/lib/. Short overview: - features.in/Makefile: lib/ support (supporting VE images requires dynamic modifications to image.in/Makefile before starting the build; the most natural way to achieve that seems to use features mechanism along with makefile include dir) - packaging format related part moved into features.in/pack (should be better prepared for diversity either) - features.in/iso renamed to features.in/build-distro - features.in/ve renamed to features.in/build-ve + NB: these could not be merged as e.g. features.in/build due to completely different script hooks - lib/image.mk renamed to lib/build.mk - image, config, log postprocessing moved downstream - added a sort of a topping in the form of lib/sugar.mk - assorted style fixups (like ifeq usage) - clean.mk: reliability fix (the problem was observed by Oleg Ivanov and me too but finally it did get the attention quantum) - reviewed, updated and extended docs + QUICKSTART: should be[come] a step-by-step guide (thanks Leo-sp50 for prodiving feedback) 2011-10-06 12:46:31 +04:00			`DATE ?= $(shell date +%Y%m%d)`
working installer iso image - s/stage2/install2/g - added pkg/lists - initial README (ru_RU.KOI8-R) - mkimage topdir is in image.in/, really (off-tree build) + initial bin/mktmpdir + BUILDDIR (works) - s/cd/iso/ - drop --with-distro (considered harmful) 2010-08-28 20:28:42 +04:00
initial kernel and metadata features This further refines the modular build by making metadata being a clearly separated feature rather than having to rely on runtime tests, and also by moving the code which cares for kernel bits of base installation (.base list) in a feature of its own. There's more to it but let's get the ball rolling first. 2012-05-08 18:59:57 +04:00			`# prefix pkglist name with its directory to form a path (relative/absolute)`
			`rlist = $(1:%=lists/%)`
			`list = $(addprefix $(PKGDIR)/,$(call rlist,$(1)))`
working installer iso image - s/stage2/install2/g - added pkg/lists - initial README (ru_RU.KOI8-R) - mkimage topdir is in image.in/, really (off-tree build) + initial bin/mktmpdir + BUILDDIR (works) - s/cd/iso/ - drop --with-distro (considered harmful) 2010-08-28 20:28:42 +04:00
initial kernel and metadata features This further refines the modular build by making metadata being a clearly separated feature rather than having to rely on runtime tests, and also by moving the code which cares for kernel bits of base installation (.base list) in a feature of its own. There's more to it but let's get the ball rolling first. 2012-05-08 18:59:57 +04:00			`# prefix/suffix group name to form a path (relative/absolute)`
			`rgroup = $(1:%=groups/%.directory)`
			`group = $(addprefix $(PKGDIR)/,$(call rgroup,$(1)))`
kernel day - drop hardwired kernel flavour from pkglists - today's std-ng lacks aufs, let's switch to un-def - second assault at KERNEL_PACKAGES_REGEXP - re-introduced kpackages (builds ok) PS: base lists: switch to grub, add udev, cleanup 2010-10-29 13:11:03 +04:00
			`# map first argument (a function) onto second one (an argument list)`
			`map = $(foreach a,$(2),$(call $(1),$(a)))`

			`# kernel package list generation; see also #24669`
			`NULL :=`
			`SPACE := $(NULL) # the officially documented way of getting a space`
official {distro,ve}/* support This is quite a large-scale change since mkimage-profiles got used to baking distributions over the last year, and virtual environments are quite different, so e.g. image.in/Makefile had to be split in two with the main part of it moved into features.in/iso/lib/. Short overview: - features.in/Makefile: lib/ support (supporting VE images requires dynamic modifications to image.in/Makefile before starting the build; the most natural way to achieve that seems to use features mechanism along with makefile include dir) - packaging format related part moved into features.in/pack (should be better prepared for diversity either) - features.in/iso renamed to features.in/build-distro - features.in/ve renamed to features.in/build-ve + NB: these could not be merged as e.g. features.in/build due to completely different script hooks - lib/image.mk renamed to lib/build.mk - image, config, log postprocessing moved downstream - added a sort of a topping in the form of lib/sugar.mk - assorted style fixups (like ifeq usage) - clean.mk: reliability fix (the problem was observed by Oleg Ivanov and me too but finally it did get the attention quantum) - reviewed, updated and extended docs + QUICKSTART: should be[come] a step-by-step guide (thanks Leo-sp50 for prodiving feedback) 2011-10-06 12:46:31 +04:00
kernel day - drop hardwired kernel flavour from pkglists - today's std-ng lacks aufs, let's switch to un-def - second assault at KERNEL_PACKAGES_REGEXP - re-introduced kpackages (builds ok) PS: base lists: switch to grub, add udev, cleanup 2010-10-29 13:11:03 +04:00			`list2re = $(subst $(SPACE),\|,$(strip $(1)))`
initial branding feature As duly noted by glebfm@, branding issues need more attention by now since only stage1/install2 got some of it so far in this regard. Hence the dedicated feature comes to the rescue (well no, it doesn't actually mess with rescue!). 2012-04-25 15:18:23 +04:00
fix kpackages() API This function's got its argument order chosen for "aesthetical" reason of $(2) following $(1) in the macros but the logical order is exactly the opposite: we care for kernel flavour much more than for module set (which is dependent upon it). So while silent dropout of kernel-image if KFLAVOURS is set but KMODULES is empty could be fixed by testing for $(2) only, it looks like a good time to fix this discrepancy altogether. 2014-09-18 20:08:08 +04:00			`# args: KFLAVOURS, KMODULES`
			`# NB: $(2) could be empty`
			`kpackages = $(and $(1), \`
			`^kernel-(image\|modules-($(call list2re,$(2))))-($(call list2re,$(1)))$$)`
initial branding feature As duly noted by glebfm@, branding issues need more attention by now since only stage1/install2 got some of it so far in this regard. Hence the dedicated feature comes to the rescue (well no, it doesn't actually mess with rescue!). 2012-04-25 15:18:23 +04:00
			`# arg: branding subpackages`
added plymouth feature An initial draft of it was done half a year ago but several tricky thingies had kept the code from showing up as it was rather brittle and incomplete. This implementation involves quite a few changes all over the place but finally works good enough for live and installer images. Please pay attention to the versions of these packages: - installer-feature-setup-plymouth (0.3.2-alt1+) - branding-altlinux-sisyphus (20110706-alt2+ if used) - plymouth (0.8.3-alt20.git20110406+) See also: - http://www.altlinux.org/Branding - http://www.altlinux.org/Plymouth 2012-06-13 23:07:10 +04:00			`branding = $(and $(1),^branding-$(BRANDING)-($(call list2re,$(1)))$$)`