VA
/
virtual-appliance
1
0
Fork 0
Code Issues Pull Requests Releases 6 Wiki Activity
virtual-appliance/Makefile

491 lines
17 KiB
Makefile
Raw Normal View History

Default chroot directory should not fail when used in the appliance's Makefile
2011-07-07 03:40:20 +02:00
APPLIANCE ?= base
Allow images/packages to build in a different directory By setting the VABUILDER_OUTPUT Makefile variable, one can have images and packages saved to and retrieved from that directory instead of the default (CURDIR). This can be use to, e.g., have different profile's builds in different directories (instead of having to give images different filenames, etc.).
2015-09-14 12:00:37 +02:00
VABUILDER_OUTPUT := $(CURDIR)
refactor how /etc/portage files are handled
2018-12-02 05:46:12 +01:00
CHROOT := $(VABUILDER_OUTPUT)/build/$(APPLIANCE)
s/PKGDIR/VA_PKGDIR/
2018-10-27 08:26:16 +02:00
VA_PKGDIR = $(VABUILDER_OUTPUT)/packages
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
DISTDIR = $(CURDIR)/distfiles
use additional overlays/repositories
2021-02-05 20:45:54 +01:00
REPO_DIR = $(CURDIR)/repos
REPO_NAMES =
builds the kernel separately to avoid having to rebuild it for any appliance
2021-05-22 19:53:34 +02:00
KERNEL_DIR = $(CURDIR)/kernel
use additional overlays/repositories
2021-02-05 20:45:54 +01:00
PORTAGE_DIR = $(REPO_DIR)/gentoo
I learned a lot about Makefiles :D So, basically I re-architeched things a bit: The appliance/Makefile.inc fiels are now appliance/Makefile (again). The main Makefile will call "make -C appliance preinstall" and "postinstall" (and in future "clean"). So I got rid of the ugly make variables/include thing. Some of the main Makefile's variables are exported to the sub-makes. Appliances don't really need $(APPLIANCE) anymore as the appliance directory is their CWD. Added some new targets and smarter targets. I can do more with this, but it's a big improvment from last time. Still learning a lot of Makefile magic (been reading other people's Makefiles). Verified that "make -j3" works (at least on the base appliance) but will kill your hard drive :D Introduced "profiles" Which are files with variables you want to override. The file will be "include"ed by the main Makefile. For example, I have a file, "local.cfg" that looks like this: --- 8< ----------------------------- CHROOT = /var/scratch/marduk/vabuild HEADLESS = YES PRUNE_CRITICAL = NO VIRTIO = YES TIMEZONE = EST5EDT DISK_SIZE = 60.0G SWAP_SIZE = 48 PKGDIR = /var/scratch/packages NBD_DEV = /dev/nbd8 all: qcow --- 8< ------------------------------ Then, e.g. i can run "make PROFILE=local APPLIANCE=kde". If you don't specify a PROFILE variable, then it will default to the empty string, which means the main Makefile will attempt to include .cfg So, for example i have: $ ln -s local.cfg .cfg $ make APPLIANCE=kde Don't set PROFILE inside your .cfg file (why would you?). Also, if the [pro]file does not exist, the include fails silently. I will put this info in the wiki eventually...
2010-11-14 00:22:18 +01:00
HOSTNAME = $(APPLIANCE)
Allow images/packages to build in a different directory By setting the VABUILDER_OUTPUT Makefile variable, one can have images and packages saved to and retrieved from that directory instead of the default (CURDIR). This can be use to, e.g., have different profile's builds in different directories (instead of having to give images different filenames, etc.).
2015-09-14 12:00:37 +02:00
IMAGES = $(VABUILDER_OUTPUT)/images
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
RAW_IMAGE = $(IMAGES)/$(APPLIANCE).img
QCOW_IMAGE = $(IMAGES)/$(APPLIANCE).qcow
VMDK_IMAGE = $(IMAGES)/$(APPLIANCE).vmdk
allow switching between vmdk images with IDE or SCSI controller
2021-02-05 16:35:27 +01:00
VMDK_TYPE = IDE
allow the creation of ova images requires open-vmdk, a gentoo ebuild is available here: https://git.unitas-network.de/Gentoo/unitas-misc/src/branch/master/app-emulation/open-vmdk
2021-02-05 16:41:23 +01:00
OVA_IMAGE = $(IMAGES)/$(APPLIANCE).ova
OVA_NUM_CPUS = 1
OVA_MEM_SIZE = 1024
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
XVA_IMAGE = $(IMAGES)/$(APPLIANCE).xva
LST_FILE = $(IMAGES)/$(APPLIANCE)-packages.lst
Change the way we create checksums
2015-09-14 13:09:15 +02:00
CHECKSUMS = $(IMAGES)/SHA256SUMS
Makefile: use /var/tmp instead of /tmp systemd (by default) opens with a clean /tmp, so copying a file into it will get cleared out (it's a tmpfs mount).
2015-12-17 22:25:03 +01:00
STAGE3 = $(CHROOT)/var/tmp/stage3
COMPILE_OPTIONS = $(CHROOT)/var/tmp/compile_options
SOFTWARE = $(CHROOT)/var/tmp/software
builds the kernel separately to avoid having to rebuild it for any appliance
2021-05-22 19:53:34 +02:00
KERNEL_SRC = $(CHROOT)/var/tmp/kernel_src
Makefile: use /var/tmp instead of /tmp systemd (by default) opens with a clean /tmp, so copying a file into it will get cleared out (it's a tmpfs mount).
2015-12-17 22:25:03 +01:00
KERNEL = $(CHROOT)/var/tmp/kernel
GRUB = $(CHROOT)/var/tmp/grub
PREPROOT = $(CHROOT)/var/tmp/preproot
SYSTOOLS = $(CHROOT)/var/tmp/systools
Allow images/packages to build in a different directory By setting the VABUILDER_OUTPUT Makefile variable, one can have images and packages saved to and retrieved from that directory instead of the default (CURDIR). This can be use to, e.g., have different profile's builds in different directories (instead of having to give images different filenames, etc.).
2015-09-14 12:00:37 +02:00
STAGE4_TARBALL = $(VABUILDER_OUTPUT)/images/$(APPLIANCE).tar.xz
I learned a lot about Makefiles :D So, basically I re-architeched things a bit: The appliance/Makefile.inc fiels are now appliance/Makefile (again). The main Makefile will call "make -C appliance preinstall" and "postinstall" (and in future "clean"). So I got rid of the ugly make variables/include thing. Some of the main Makefile's variables are exported to the sub-makes. Appliances don't really need $(APPLIANCE) anymore as the appliance directory is their CWD. Added some new targets and smarter targets. I can do more with this, but it's a big improvment from last time. Still learning a lot of Makefile magic (been reading other people's Makefiles). Verified that "make -j3" works (at least on the base appliance) but will kill your hard drive :D Introduced "profiles" Which are files with variables you want to override. The file will be "include"ed by the main Makefile. For example, I have a file, "local.cfg" that looks like this: --- 8< ----------------------------- CHROOT = /var/scratch/marduk/vabuild HEADLESS = YES PRUNE_CRITICAL = NO VIRTIO = YES TIMEZONE = EST5EDT DISK_SIZE = 60.0G SWAP_SIZE = 48 PKGDIR = /var/scratch/packages NBD_DEV = /dev/nbd8 all: qcow --- 8< ------------------------------ Then, e.g. i can run "make PROFILE=local APPLIANCE=kde". If you don't specify a PROFILE variable, then it will default to the empty string, which means the main Makefile will attempt to include .cfg So, for example i have: $ ln -s local.cfg .cfg $ make APPLIANCE=kde Don't set PROFILE inside your .cfg file (why would you?). Also, if the [pro]file does not exist, the include fails silently. I will put this info in the wiki eventually...
2010-11-14 00:22:18 +01:00
VIRTIO = NO
TIMEZONE = UTC
DISK_SIZE = 6.0G
SWAP_SIZE = 30
SWAP_FILE = $(CHROOT)/.swap
s/ARCH/VA_ARCH/
2018-10-27 08:24:05 +02:00
VA_ARCH = amd64
KERNEL_CONFIG = configs/kernel.config.$(VA_ARCH)
builds the kernel separately to avoid having to rebuild it for any appliance
2021-05-22 19:53:34 +02:00
KERNEL_PATH = $(CHROOT)/usr/src/kernel-path
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
MAKEOPTS = -j5 -l5.64
Added global Makefile option to enable sshd in the appliance
2011-01-21 00:17:32 +01:00
ENABLE_SSHD = NO
Makefile: make changing of root password and removing or portage tree both optional
2010-12-20 05:04:11 +01:00
CHANGE_PASSWORD = YES
I learned a lot about Makefiles :D So, basically I re-architeched things a bit: The appliance/Makefile.inc fiels are now appliance/Makefile (again). The main Makefile will call "make -C appliance preinstall" and "postinstall" (and in future "clean"). So I got rid of the ugly make variables/include thing. Some of the main Makefile's variables are exported to the sub-makes. Appliances don't really need $(APPLIANCE) anymore as the appliance directory is their CWD. Added some new targets and smarter targets. I can do more with this, but it's a big improvment from last time. Still learning a lot of Makefile magic (been reading other people's Makefiles). Verified that "make -j3" works (at least on the base appliance) but will kill your hard drive :D Introduced "profiles" Which are files with variables you want to override. The file will be "include"ed by the main Makefile. For example, I have a file, "local.cfg" that looks like this: --- 8< ----------------------------- CHROOT = /var/scratch/marduk/vabuild HEADLESS = YES PRUNE_CRITICAL = NO VIRTIO = YES TIMEZONE = EST5EDT DISK_SIZE = 60.0G SWAP_SIZE = 48 PKGDIR = /var/scratch/packages NBD_DEV = /dev/nbd8 all: qcow --- 8< ------------------------------ Then, e.g. i can run "make PROFILE=local APPLIANCE=kde". If you don't specify a PROFILE variable, then it will default to the empty string, which means the main Makefile will attempt to include .cfg So, for example i have: $ ln -s local.cfg .cfg $ make APPLIANCE=kde Don't set PROFILE inside your .cfg file (why would you?). Also, if the [pro]file does not exist, the include fails silently. I will put this info in the wiki eventually...
2010-11-14 00:22:18 +01:00
HEADLESS = NO
New Makefile variable: EXTERNAL_KERNEL If set to YES, then the kernel sources will not be installed and a kernel is not built, nor is grub installed/configured. This is can be useful when building appliances for hypervisors such as Xen and Qemu/KVM which can run from external kernel/initramfs configurations. Default is NO
2011-02-05 06:06:23 +01:00
EXTERNAL_KERNEL = NO
* New Makefile variable PKGLIST. When set to 1 will create a file outside the appliance with the list of installed packages on that appliance. PKGLIST is off by default. * Works with baselayout-2 stage3s, including the fix for the current broken stage3 tarballs. * The new stage3 tarballs are much more limited as far as what dev nodes are included. In addition to being broken stage3s themselves, it also broke the UDEV=NO option. So I have included my own device node tarball which is installed when UDEV=NO. * Put double quotes around hostname in /etc/conf.d/hostname.
2011-06-23 03:42:59 +02:00
PKGLIST = 0
New DASH Makefile variable, if set to "YES", will install app-shells/dash and set it as the login shell for root.
2011-04-06 16:25:05 +02:00
DASH = NO
Set the locale By default it's set to en_US.utf8
2015-09-26 22:57:49 +02:00
LOCALE ?= en_US.utf8
I learned a lot about Makefiles :D So, basically I re-architeched things a bit: The appliance/Makefile.inc fiels are now appliance/Makefile (again). The main Makefile will call "make -C appliance preinstall" and "postinstall" (and in future "clean"). So I got rid of the ugly make variables/include thing. Some of the main Makefile's variables are exported to the sub-makes. Appliances don't really need $(APPLIANCE) anymore as the appliance directory is their CWD. Added some new targets and smarter targets. I can do more with this, but it's a big improvment from last time. Still learning a lot of Makefile magic (been reading other people's Makefiles). Verified that "make -j3" works (at least on the base appliance) but will kill your hard drive :D Introduced "profiles" Which are files with variables you want to override. The file will be "include"ed by the main Makefile. For example, I have a file, "local.cfg" that looks like this: --- 8< ----------------------------- CHROOT = /var/scratch/marduk/vabuild HEADLESS = YES PRUNE_CRITICAL = NO VIRTIO = YES TIMEZONE = EST5EDT DISK_SIZE = 60.0G SWAP_SIZE = 48 PKGDIR = /var/scratch/packages NBD_DEV = /dev/nbd8 all: qcow --- 8< ------------------------------ Then, e.g. i can run "make PROFILE=local APPLIANCE=kde". If you don't specify a PROFILE variable, then it will default to the empty string, which means the main Makefile will attempt to include .cfg So, for example i have: $ ln -s local.cfg .cfg $ make APPLIANCE=kde Don't set PROFILE inside your .cfg file (why would you?). Also, if the [pro]file does not exist, the include fails silently. I will put this info in the wiki eventually...
2010-11-14 00:22:18 +01:00
M4 = m4
Makefile: EMERGE variable tweaks Don't (need to) use the full path and make --jobs argument smarter.
2018-10-27 21:01:37 +02:00
EMERGE = emerge --jobs=$(shell nproc --all)
I learned a lot about Makefiles :D So, basically I re-architeched things a bit: The appliance/Makefile.inc fiels are now appliance/Makefile (again). The main Makefile will call "make -C appliance preinstall" and "postinstall" (and in future "clean"). So I got rid of the ugly make variables/include thing. Some of the main Makefile's variables are exported to the sub-makes. Appliances don't really need $(APPLIANCE) anymore as the appliance directory is their CWD. Added some new targets and smarter targets. I can do more with this, but it's a big improvment from last time. Still learning a lot of Makefile magic (been reading other people's Makefiles). Verified that "make -j3" works (at least on the base appliance) but will kill your hard drive :D Introduced "profiles" Which are files with variables you want to override. The file will be "include"ed by the main Makefile. For example, I have a file, "local.cfg" that looks like this: --- 8< ----------------------------- CHROOT = /var/scratch/marduk/vabuild HEADLESS = YES PRUNE_CRITICAL = NO VIRTIO = YES TIMEZONE = EST5EDT DISK_SIZE = 60.0G SWAP_SIZE = 48 PKGDIR = /var/scratch/packages NBD_DEV = /dev/nbd8 all: qcow --- 8< ------------------------------ Then, e.g. i can run "make PROFILE=local APPLIANCE=kde". If you don't specify a PROFILE variable, then it will default to the empty string, which means the main Makefile will attempt to include .cfg So, for example i have: $ ln -s local.cfg .cfg $ make APPLIANCE=kde Don't set PROFILE inside your .cfg file (why would you?). Also, if the [pro]file does not exist, the include fails silently. I will put this info in the wiki eventually...
2010-11-14 00:22:18 +01:00
M4_DEFS = -D HOSTNAME=$(HOSTNAME)
M4C = $(M4) $(M4_DEFS)
USEPKG = --usepkg --binpkg-respect-use=y
Since RIT.edu's mirror is 30+ days behind, switch rsync mirror to GA Tech
2011-06-25 04:48:07 +02:00
RSYNC_MIRROR = rsync://rsync.gtlib.gatech.edu/gentoo/
Makefile: Make the kernel target inside the chroot
2015-02-27 22:20:43 +01:00
KERNEL_PKG = gentoo-sources
Move appliances/configs/scripts to seperate directories. Instead of having everything in the root directory, split them in seperate directories (appliances, scripts, & configs). This makes things a little tidier. Also added a now Makefile target, appliance-list, that prints a list of the available appliances. The split directory change made this easier.
2014-06-09 04:26:17 +02:00
WORLD = appliances/$(APPLIANCE)/world
allowing the use of a default appliance An appliance with the name "default" can be created, and its configuration is used as the basis for all other appliances.
2021-02-07 18:31:01 +01:00
WORLD_DEFAULT = appliances/default/world
Add EXTRA_WORLD Makefile variable to add extra packages to world
2011-11-16 12:44:32 +01:00
EXTRA_WORLD =
I learned a lot about Makefiles :D So, basically I re-architeched things a bit: The appliance/Makefile.inc fiels are now appliance/Makefile (again). The main Makefile will call "make -C appliance preinstall" and "postinstall" (and in future "clean"). So I got rid of the ugly make variables/include thing. Some of the main Makefile's variables are exported to the sub-makes. Appliances don't really need $(APPLIANCE) anymore as the appliance directory is their CWD. Added some new targets and smarter targets. I can do more with this, but it's a big improvment from last time. Still learning a lot of Makefile magic (been reading other people's Makefiles). Verified that "make -j3" works (at least on the base appliance) but will kill your hard drive :D Introduced "profiles" Which are files with variables you want to override. The file will be "include"ed by the main Makefile. For example, I have a file, "local.cfg" that looks like this: --- 8< ----------------------------- CHROOT = /var/scratch/marduk/vabuild HEADLESS = YES PRUNE_CRITICAL = NO VIRTIO = YES TIMEZONE = EST5EDT DISK_SIZE = 60.0G SWAP_SIZE = 48 PKGDIR = /var/scratch/packages NBD_DEV = /dev/nbd8 all: qcow --- 8< ------------------------------ Then, e.g. i can run "make PROFILE=local APPLIANCE=kde". If you don't specify a PROFILE variable, then it will default to the empty string, which means the main Makefile will attempt to include .cfg So, for example i have: $ ln -s local.cfg .cfg $ make APPLIANCE=kde Don't set PROFILE inside your .cfg file (why would you?). Also, if the [pro]file does not exist, the include fails silently. I will put this info in the wiki eventually...
2010-11-14 00:22:18 +01:00
refactor how /etc/portage files are handled
2018-12-02 05:46:12 +01:00
# /etc/portage targets
base_etc_portage := $(wildcard configs/portage/*)
etc_portage := $(patsubst configs/portage/%,$(CHROOT)/etc/portage/%,$(base_etc_portage))
allowing the use of a default appliance An appliance with the name "default" can be created, and its configuration is used as the basis for all other appliances.
2021-02-07 18:31:01 +01:00
default_package_files := $(wildcard appliances/default/package.*)
refactor how /etc/portage files are handled
2018-12-02 05:46:12 +01:00
appliance_package_files := $(wildcard appliances/$(APPLIANCE)/package.*)
allowing the use of a default appliance An appliance with the name "default" can be created, and its configuration is used as the basis for all other appliances.
2021-02-07 18:31:01 +01:00
portage_default_package_files = $(patsubst appliances/default/package.%,$(CHROOT)/etc/portage/package.%/01default,$(default_package_files))
portage_package_files = $(patsubst appliances/$(APPLIANCE)/package.%,$(CHROOT)/etc/portage/package.%/02$(APPLIANCE),$(appliance_package_files))
fix make.conf.local
2021-02-08 19:12:27 +01:00
default_make_conf = $(wildcard appliances/default/make.conf)
refactor how /etc/portage files are handled
2018-12-02 05:46:12 +01:00
appliance_make_conf = $(wildcard appliances/$(APPLIANCE)/make.conf)
portage_make_conf_local = $(CHROOT)/etc/portage/make.conf.local
- Adjustments to current Gentoo changes - Adjustments to create the appliance on Debian - use grub-install from appliance (not from build host) - fixes
2024-04-15 09:45:56 +02:00
appliance_profile := default/linux/amd64/23.0/systemd
refactor how /etc/portage files are handled
2018-12-02 05:46:12 +01:00
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
# Allow appliance to override variables
allowing the use of a default appliance An appliance with the name "default" can be created, and its configuration is used as the basis for all other appliances.
2021-02-07 18:31:01 +01:00
-include appliances/default/default.cfg
Makefile: fix typo The line that was including the appliance-specific config had a typo. The typo was overlooked all this time because no appliance really uses this feature. Until now...
2015-12-11 02:15:10 +01:00
-include appliances/$(APPLIANCE)/$(APPLIANCE).cfg
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
# Allow user to override variables
changed PROFILE variable to profile to avoid clobbering builds
2010-12-07 02:19:37 +01:00
-include $(profile).cfg
I learned a lot about Makefiles :D So, basically I re-architeched things a bit: The appliance/Makefile.inc fiels are now appliance/Makefile (again). The main Makefile will call "make -C appliance preinstall" and "postinstall" (and in future "clean"). So I got rid of the ugly make variables/include thing. Some of the main Makefile's variables are exported to the sub-makes. Appliances don't really need $(APPLIANCE) anymore as the appliance directory is their CWD. Added some new targets and smarter targets. I can do more with this, but it's a big improvment from last time. Still learning a lot of Makefile magic (been reading other people's Makefiles). Verified that "make -j3" works (at least on the base appliance) but will kill your hard drive :D Introduced "profiles" Which are files with variables you want to override. The file will be "include"ed by the main Makefile. For example, I have a file, "local.cfg" that looks like this: --- 8< ----------------------------- CHROOT = /var/scratch/marduk/vabuild HEADLESS = YES PRUNE_CRITICAL = NO VIRTIO = YES TIMEZONE = EST5EDT DISK_SIZE = 60.0G SWAP_SIZE = 48 PKGDIR = /var/scratch/packages NBD_DEV = /dev/nbd8 all: qcow --- 8< ------------------------------ Then, e.g. i can run "make PROFILE=local APPLIANCE=kde". If you don't specify a PROFILE variable, then it will default to the empty string, which means the main Makefile will attempt to include .cfg So, for example i have: $ ln -s local.cfg .cfg $ make APPLIANCE=kde Don't set PROFILE inside your .cfg file (why would you?). Also, if the [pro]file does not exist, the include fails silently. I will put this info in the wiki eventually...
2010-11-14 00:22:18 +01:00
Set systemd container name according to profile. This allows more different profiles to with the same appliance to build simultaneously.
2015-09-14 12:16:56 +02:00
ifneq ($(profile),)
container = $(profile)-$(APPLIANCE)-build
else
container = $(APPLIANCE)-build
endif
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
PATH := $(CURDIR)/scripts:$(PATH)
use additional overlays/repositories
2021-02-05 20:45:54 +01:00
export PATH CHROOT container PORTAGE_DIR REPO_DIR REPO_NAMES VA_PKGDIR DISTDIR VA_ARCH
Set systemd container name according to profile. This allows more different profiles to with the same appliance to build simultaneously.
2015-09-14 12:16:56 +02:00
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
inroot := systemd-nspawn --quiet \
--directory=$(CHROOT) \
Set systemd container name according to profile. This allows more different profiles to with the same appliance to build simultaneously.
2015-09-14 12:16:56 +02:00
--machine=$(container) \
fixes to avoid lots of error messages - disable cgroups portage feature - allow CAP_NET_ADMIN for the use of systemd-nspawn (https://github.com/systemd/systemd/issues/13308)
2021-02-05 16:09:03 +01:00
--capability=CAP_NET_ADMIN \
new gentoo portage locations
2021-02-05 13:27:21 +01:00
--bind=$(PORTAGE_DIR):/var/db/repos/gentoo \
use additional overlays/repositories
2021-02-05 20:45:54 +01:00
$(foreach repo,$(REPO_NAMES),--bind=$(REPO_DIR)/$(repo):/var/db/repos/$(repo) ) \
new gentoo portage locations
2021-02-05 13:27:21 +01:00
--bind=$(VA_PKGDIR):/var/cache/binpkgs \
--bind=$(DISTDIR):/var/cache/distfiles
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
s/ARCH/VA_ARCH/
2018-10-27 08:24:05 +02:00
ifeq ($(VA_ARCH),x86)
Actually enable 32bit builds. This only works with paravirt so far. Need to create a kernel .config for x86.
2012-12-21 20:12:25 +01:00
inroot := linux32 $(inroot)
endif
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
stage4-exists := $(wildcard $(STAGE4_TARBALL))
I learned a lot about Makefiles :D So, basically I re-architeched things a bit: The appliance/Makefile.inc fiels are now appliance/Makefile (again). The main Makefile will call "make -C appliance preinstall" and "postinstall" (and in future "clean"). So I got rid of the ugly make variables/include thing. Some of the main Makefile's variables are exported to the sub-makes. Appliances don't really need $(APPLIANCE) anymore as the appliance directory is their CWD. Added some new targets and smarter targets. I can do more with this, but it's a big improvment from last time. Still learning a lot of Makefile magic (been reading other people's Makefiles). Verified that "make -j3" works (at least on the base appliance) but will kill your hard drive :D Introduced "profiles" Which are files with variables you want to override. The file will be "include"ed by the main Makefile. For example, I have a file, "local.cfg" that looks like this: --- 8< ----------------------------- CHROOT = /var/scratch/marduk/vabuild HEADLESS = YES PRUNE_CRITICAL = NO VIRTIO = YES TIMEZONE = EST5EDT DISK_SIZE = 60.0G SWAP_SIZE = 48 PKGDIR = /var/scratch/packages NBD_DEV = /dev/nbd8 all: qcow --- 8< ------------------------------ Then, e.g. i can run "make PROFILE=local APPLIANCE=kde". If you don't specify a PROFILE variable, then it will default to the empty string, which means the main Makefile will attempt to include .cfg So, for example i have: $ ln -s local.cfg .cfg $ make APPLIANCE=kde Don't set PROFILE inside your .cfg file (why would you?). Also, if the [pro]file does not exist, the include fails silently. I will put this info in the wiki eventually...
2010-11-14 00:22:18 +01:00
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
COPY_ARGS = --exclude-from=configs/rsync-excludes
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
Makefile: make changing of root password and removing or portage tree both optional
2010-12-20 05:04:11 +01:00
ifeq ($(CHANGE_PASSWORD),YES)
New makefile variable, ROOT_PASSWORD, to set the (encrypted) root password
2011-01-12 04:47:14 +01:00
ifdef ROOT_PASSWORD
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
change_password = RUN usermod --password '$(ROOT_PASSWORD)' root
New makefile variable, ROOT_PASSWORD, to set the (encrypted) root password
2011-01-12 04:47:14 +01:00
else
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
change_password = RUN passwd --delete root
New makefile variable, ROOT_PASSWORD, to set the (encrypted) root password
2011-01-12 04:47:14 +01:00
endif
Makefile: make changing of root password and removing or portage tree both optional
2010-12-20 05:04:11 +01:00
endif
Makefile: created "inroot" macro for running commands in the chroot
2011-02-25 05:20:38 +01:00
gcc_config = $(inroot) gcc-config 1
Minor changes to make kde/unstable build again
2010-11-27 22:43:40 +01:00
use labels to create fstab use swap partition if available update python (3.11) fix fetching stage3
2023-06-02 18:02:49 +02:00
ifneq ($(shell grep 'CONFIG_MODULES=y' $(KERNEL_CONFIG)), )
KERNEL_MODULES_PREPARE = modules_prepare
endif
- Adjustments to current Gentoo changes - Adjustments to create the appliance on Debian - use grub-install from appliance (not from build host) - fixes
2024-04-15 09:45:56 +02:00
export APPLIANCE ACCEPT_KEYWORDS CHROOT EMERGE HEADLESS M4 M4C inroot gcc_config
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
export HOSTNAME MAKEOPTS TIMEZONE USEPKG WORLD
Makefile: export RSYNC_MIRROR Another forgotten artifact from cs bcbd924efc3a.
2015-02-21 14:17:08 +01:00
export USEPKG RSYNC_MIRROR
builds the kernel separately to avoid having to rebuild it for any appliance
2021-05-22 19:53:34 +02:00
export EXTERNAL_KERNEL KERNEL_PKG KERNEL_PATH KERNEL_CONFIG
I learned a lot about Makefiles :D So, basically I re-architeched things a bit: The appliance/Makefile.inc fiels are now appliance/Makefile (again). The main Makefile will call "make -C appliance preinstall" and "postinstall" (and in future "clean"). So I got rid of the ugly make variables/include thing. Some of the main Makefile's variables are exported to the sub-makes. Appliances don't really need $(APPLIANCE) anymore as the appliance directory is their CWD. Added some new targets and smarter targets. I can do more with this, but it's a big improvment from last time. Still learning a lot of Makefile magic (been reading other people's Makefiles). Verified that "make -j3" works (at least on the base appliance) but will kill your hard drive :D Introduced "profiles" Which are files with variables you want to override. The file will be "include"ed by the main Makefile. For example, I have a file, "local.cfg" that looks like this: --- 8< ----------------------------- CHROOT = /var/scratch/marduk/vabuild HEADLESS = YES PRUNE_CRITICAL = NO VIRTIO = YES TIMEZONE = EST5EDT DISK_SIZE = 60.0G SWAP_SIZE = 48 PKGDIR = /var/scratch/packages NBD_DEV = /dev/nbd8 all: qcow --- 8< ------------------------------ Then, e.g. i can run "make PROFILE=local APPLIANCE=kde". If you don't specify a PROFILE variable, then it will default to the empty string, which means the main Makefile will attempt to include .cfg So, for example i have: $ ln -s local.cfg .cfg $ make APPLIANCE=kde Don't set PROFILE inside your .cfg file (why would you?). Also, if the [pro]file does not exist, the include fails silently. I will put this info in the wiki eventually...
2010-11-14 00:22:18 +01:00
Makefile: make the default target "stage4" instead of "image"
2015-03-01 02:55:57 +01:00
all: stage4
Initial commit
2010-07-09 05:22:37 +02:00
Makefile: make the $(RAW_IMAGE) target install the stage4 files. The raw image making was kind of split up, with different targets to create the image, partition, copy files, install grub, etc. This change makes it all one target. After "make image" is done, or, e.g., "make images/base.img" then the resulting file will be built and contain all the necessary files. This make the $(RAW_IMAGE) target more uniform with the other image/ targets. It will also make the other image/ targets easier to satify.
2015-02-28 23:27:39 +01:00
image: $(RAW_IMAGE)
Initial commit
2010-07-09 05:22:37 +02:00
Makefile: use the git repo for the PORTAGE_DIR Now more rsync'ing snapshots. We can just clone/pull the repo on github.
2015-12-17 22:25:59 +01:00
sync_portage: $(PORTAGE_DIR)
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Grabbing latest portage
Makefile: use the git repo for the PORTAGE_DIR Now more rsync'ing snapshots. We can just clone/pull the repo on github.
2015-12-17 22:25:59 +01:00
git -C $(PORTAGE_DIR) pull
touch $(PORTAGE_DIR)
Don't autosync portage.
2013-08-25 11:24:46 +02:00
Makefile: use the git repo for the PORTAGE_DIR Now more rsync'ing snapshots. We can just clone/pull the repo on github.
2015-12-17 22:25:59 +01:00
$(PORTAGE_DIR):
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Grabbing the portage tree
fix gentoo github url
2023-05-30 19:45:23 +02:00
git clone --depth=1 https://github.com/gentoo/gentoo.git $(PORTAGE_DIR)
Cleaned up Makefile and hopefully made it more modular. Added preinstall and postinstall scripts for additional software
2010-07-10 20:04:04 +02:00
refactor how /etc/portage files are handled
2018-12-02 05:46:12 +01:00
$(CHROOT)/etc/portage/%: configs/portage/%
COPY --recursive $< /etc/portage/
use labels to create fstab use swap partition if available update python (3.11) fix fetching stage3
2023-06-02 18:02:49 +02:00
fstab:
@print Create new /etc/fstab
- Adjustments to current Gentoo changes - Adjustments to create the appliance on Debian - use grub-install from appliance (not from build host) - fixes
2024-04-15 09:45:56 +02:00
env echo -e "# <fs>\t\t<mountpoint>\t<type>\t<opts>\t<dump/pass>" > $(CHROOT)/etc/fstab
env echo -e "LABEL=ROOT\t/\t\text4\tnoatime\t1 1" >> $(CHROOT)/etc/fstab
env echo -e "/.swap\t\tnone\t\tswap\tsw\t0 0" >> $(CHROOT)/etc/fstab
env echo -e "#LABEL=SWAP\tnone\t\tswap\tsw\t0 0" >> $(CHROOT)/etc/fstab
Numerous updates: * Exclude some files from the stage3 tarball to be installed in the chroot. This reduces the number of etc-updates that need to be process. * Manually eselect profile. This is needed now because /etc/portage/make.profile is excluded above. * Use m4 and a template (in file) to create /etc/fstab instead of using sed. * Add a "software" target. This is mainly used for development.
2018-12-09 01:12:33 +01:00
use labels to create fstab use swap partition if available update python (3.11) fix fetching stage3
2023-06-02 18:02:49 +02:00
$(PREPROOT): $(STAGE3) $(PORTAGE_DIR) $(foreach repo,$(REPO_NAMES),$(REPO_DIR)/$(repo)) fstab $(etc_portage) $(portage_default_package_files) $(portage_package_files)
Numerous updates: * Exclude some files from the stage3 tarball to be installed in the chroot. This reduces the number of etc-updates that need to be process. * Manually eselect profile. This is needed now because /etc/portage/make.profile is excluded above. * Use m4 and a template (in file) to create /etc/fstab instead of using sed. * Add a "software" target. This is mainly used for development.
2018-12-09 01:12:33 +01:00
mkdir -p $(VA_PKGDIR) $(DISTDIR)
Makefile: One more echo/print change
2018-10-27 20:49:42 +02:00
@print Creating swap file: `basename $(SWAP_FILE)`
Merge SWAP_FILE and SYSCONFIG targets into PREPROOT They were small targets and PREPROOT is pretty much responsible for that anyway.
2015-03-01 02:06:24 +01:00
dd if=/dev/zero of=$(SWAP_FILE) bs=1M count=$(SWAP_SIZE)
/sbin/mkswap $(SWAP_FILE)
Makefile:preproot: Make sure we've always got a local copy of resolv.conf Or else network will fail inside the chroot.
2015-02-27 21:09:13 +01:00
rm -f $(CHROOT)/etc/resolv.conf
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
COPY -L /etc/resolv.conf /etc/resolv.conf
Makefile: Make the preproot target inside the chroot
2015-02-27 23:05:17 +01:00
touch $(PREPROOT)
Cleaned up Makefile and hopefully made it more modular. Added preinstall and postinstall scripts for additional software
2010-07-10 20:04:04 +02:00
stage3 tarball is now an xz archive
2021-02-05 12:27:13 +01:00
stage3-$(VA_ARCH).tar.xz:
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print You do not have a stage3 tarball. Consider \"make sync_stage3\"
Don't autosync the stage3 tarball.
2013-08-26 23:21:17 +02:00
@exit 1
sync_stage3:
stage3 tarball is now an xz archive
2021-02-05 12:27:13 +01:00
fetch-stage3 --systemd --outfile=stage3-$(VA_ARCH).tar.xz $(VA_ARCH)
Don't autosync the stage3 tarball.
2013-08-26 23:21:17 +02:00
stage3 tarball is now an xz archive
2021-02-05 12:27:13 +01:00
$(STAGE3): stage3-$(VA_ARCH).tar.xz configs/stage3-tarball-excludes
Various fixes
2010-11-06 09:41:15 +01:00
mkdir -p $(CHROOT)
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
ifdef stage4-exists
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Using stage4 tarball: `basename $(STAGE4_TARBALL)`
Remove "archiving" options from tar commands. GNU Tar can (usually) handle this automagically
2013-10-13 17:56:20 +02:00
tar xpf "$(STAGE4_TARBALL)" -C $(CHROOT)
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
else
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Using stage3 tarball
stage3 tarball is now an xz archive
2021-02-05 12:27:13 +01:00
tar xpf stage3-$(VA_ARCH).tar.xz -C $(CHROOT) --exclude-from=configs/stage3-tarball-excludes
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
endif
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
rm -f $(CHROOT)/etc/localtime
Makefile: Make the stage3 target inside the chroot Then we don't have to manually clean it (it gets clean on the stage4 target).
2015-02-27 21:37:14 +01:00
touch $(STAGE3)
Cleaned up Makefile and hopefully made it more modular. Added preinstall and postinstall scripts for additional software
2010-07-10 20:04:04 +02:00
use additional overlays/repositories
2021-02-05 20:45:54 +01:00
sync_repos: $(foreach repo,$(REPO_NAMES),$(REPO_DIR)/$(repo))
@print Updating the repositories
$(foreach repo,$(REPO_NAMES),git -C $(REPO_DIR)/$(repo) pull;touch $(REPO_DIR)/$(repo);)
$(foreach repo,$(REPO_NAMES),$(REPO_DIR)/$(repo)):
@print Grabbing a repository
git clone --depth=1 $(REPO_URI_$(subst $(REPO_DIR)/,,$@)) $@
$(CHROOT)/etc/portage/repos.conf: $(foreach repo,$(REPO_NAMES),$(REPO_DIR)/$(repo))
$(foreach repo,$(REPO_NAMES),\
echo "[$(repo)]" >>$@;\
echo "location = /var/db/repos/$(repo)" >>$@;\
echo "auto-sync = no" >>$@;\
echo "" >>$@;\
)
touch $@
allowing the use of a default appliance An appliance with the name "default" can be created, and its configuration is used as the basis for all other appliances.
2021-02-07 18:31:01 +01:00
$(CHROOT)/etc/portage/package.%/01default: appliances/default/package.% $(STAGE3)
mkdir -p `dirname $@`
cp $< $@
use additional overlays/repositories
2021-02-05 20:45:54 +01:00
allowing the use of a default appliance An appliance with the name "default" can be created, and its configuration is used as the basis for all other appliances.
2021-02-07 18:31:01 +01:00
$(CHROOT)/etc/portage/package.%/02$(APPLIANCE): appliances/$(APPLIANCE)/package.% $(STAGE3)
refactor how /etc/portage files are handled
2018-12-02 05:46:12 +01:00
mkdir -p `dirname $@`
cp $< $@
fix make.conf.local
2021-02-08 19:12:27 +01:00
$(portage_make_conf_local): $(default_make_conf) $(appliance_make_conf)
if [ -f "$(default_make_conf)" ] ; \
fix creation without default appliance
2021-02-08 09:46:23 +01:00
then COPY $(default_make_conf) /etc/portage/make.conf.local; \
fi
fix make.conf.local
2021-02-08 19:12:27 +01:00
if [ -f "$(appliance_make_conf)" ] ; \
then cat $(appliance_make_conf) >> $(portage_make_conf_local); \
fix creation without default appliance
2021-02-08 09:46:23 +01:00
fi
touch $@
refactor how /etc/portage files are handled
2018-12-02 05:46:12 +01:00
Numerous updates: * Exclude some files from the stage3 tarball to be installed in the chroot. This reduces the number of etc-updates that need to be process. * Manually eselect profile. This is needed now because /etc/portage/make.profile is excluded above. * Use m4 and a template (in file) to create /etc/fstab instead of using sed. * Add a "software" target. This is mainly used for development.
2018-12-09 01:12:33 +01:00
$(CHROOT)/var/tmp/profile: $(STAGE3)
RUN eselect profile set $(appliance_profile)
touch $@
builds the kernel separately to avoid having to rebuild it for any appliance
2021-05-22 19:53:34 +02:00
$(KERNEL_PATH): $(STAGE3) $(KERNEL_CONFIG)
ifneq ($(EXTERNAL_KERNEL),YES)
$(eval kernel_ebuild = $(shell basename `RUN portageq best_visible / $(KERNEL_PKG)`))
$(eval kernel_name = $(shell echo $(kernel_ebuild) | sed -e 's/\(..*\)-sources-\(..*\)/linux-\2-\1/' -e 's/\(..*\)-\(r[0-9]*\)-\(..*\)/\1-\3-\2/'))
$(eval kernel_config_checksum = $(shell sha1sum $(KERNEL_CONFIG) | cut -c -40))
echo -n "$(KERNEL_DIR)/$(kernel_name)/$(kernel_config_checksum)" > $@
else
echo "NONE" > $@
endif
$(KERNEL_SRC): $(KERNEL_PATH)
ifneq ($(EXTERNAL_KERNEL),YES)
if [ ! -f $(shell cat $(KERNEL_PATH))/Makefile ] ; then \
RUN $(EMERGE) --oneshot --noreplace $(USEPKG) sys-kernel/$(KERNEL_PKG); \
cp -a $(CHROOT)/usr/src/linux-*/* $(shell cat $(KERNEL_PATH)); \
RUN $(EMERGE) -C sys-kernel/$(KERNEL_PKG); \
cp $(KERNEL_CONFIG) $(shell cat $(KERNEL_PATH))/.config; \
use labels to create fstab use swap partition if available update python (3.11) fix fetching stage3
2023-06-02 18:02:49 +02:00
RUN make -C /usr/src/linux MAKEOPTS=$(MAKEOPTS) oldconfig $(KERNEL_MODULES_PREPARE); \
builds the kernel separately to avoid having to rebuild it for any appliance
2021-05-22 19:53:34 +02:00
fi
endif
touch $(KERNEL_SRC)
better locale.gen handling, handling of kernel modules temporarily disabled
2022-01-19 12:03:55 +01:00
$(COMPILE_OPTIONS): $(STAGE3) $(PORTAGE_DIR) configs/make.conf.$(VA_ARCH) configs/locale.gen $(portage_default_package_files) $(portage_package_files) $(portage_make_conf_local) $(CHROOT)/var/tmp/profile $(CHROOT)/etc/portage/repos.conf $(KERNEL_SRC)
COPY configs/make.conf.$(VA_ARCH) /etc/portage/make.conf
COPY configs/locale.gen /etc/locale.gen
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
RUN locale-gen
Makefile: build compile_options inside the chroot
2015-02-27 21:44:52 +01:00
touch $(COMPILE_OPTIONS)
Cleaned up Makefile and hopefully made it more modular. Added preinstall and postinstall scripts for additional software
2010-07-10 20:04:04 +02:00
scripts: replace kernel.sh with build-kernel This newer script is Python-based and smarter than the bash script.
2016-07-24 17:08:27 +02:00
$(KERNEL): $(COMPILE_OPTIONS) $(KERNEL_CONFIG) scripts/build-kernel
New Makefile variable: EXTERNAL_KERNEL If set to YES, then the kernel sources will not be installed and a kernel is not built, nor is grub installed/configured. This is can be useful when building appliances for hypervisors such as Xen and Qemu/KVM which can run from external kernel/initramfs configurations. Default is NO
2011-02-05 06:06:23 +01:00
ifneq ($(EXTERNAL_KERNEL),YES)
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Configuring kernel
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
COPY $(KERNEL_CONFIG) /root/kernel.config
COPY scripts/build-kernel /root/build-kernel
RUN --setenv=KERNEL=$(KERNEL_PKG) \
--setenv=EMERGE="$(EMERGE)" \
--setenv=USEPKG="$(USEPKG)" \
--setenv=MAKEOPTS="$(MAKEOPTS)" \
/root/build-kernel
scripts: replace kernel.sh with build-kernel This newer script is Python-based and smarter than the bash script.
2016-07-24 17:08:27 +02:00
rm -f $(CHROOT)/root/build-kernel
New Makefile variable: EXTERNAL_KERNEL If set to YES, then the kernel sources will not be installed and a kernel is not built, nor is grub installed/configured. This is can be useful when building appliances for hypervisors such as Xen and Qemu/KVM which can run from external kernel/initramfs configurations. Default is NO
2011-02-05 06:06:23 +01:00
endif
Makefile: Make the kernel target inside the chroot
2015-02-27 22:20:43 +01:00
touch $(KERNEL)
Initial commit
2010-07-09 05:22:37 +02:00
Merge SWAP_FILE and SYSCONFIG targets into PREPROOT They were small targets and PREPROOT is pretty much responsible for that anyway.
2015-03-01 02:06:24 +01:00
$(SYSTOOLS): $(PREPROOT) $(COMPILE_OPTIONS)
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Installing standard system tools
Makefile: assume we're using the systemd stage3 So that means we don't have to uninstall eudev and replace it with systemd. Also apparently we need to set the machine-id as it doesn't appear to exist in the stage3 and I think installing systemd (which we don't do anymore) does it for you.
2016-07-23 23:16:26 +02:00
systemd-firstboot \
--root=$(CHROOT) \
--setup-machine-id \
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
--timezone=$(TIMEZONE) \
--hostname=$(HOSTNAME) \
--root-password=
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
RUN eselect locale set $(LOCALE)
New DASH Makefile variable, if set to "YES", will install app-shells/dash and set it as the login shell for root.
2011-04-06 16:25:05 +02:00
ifeq ($(DASH),YES)
Use busybox for dhcp and acpi.
2012-12-16 16:49:21 +01:00
if ! test -e "$(STAGE4_TARBALL)"; \
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
then RUN $(EMERGE) --noreplace $(USEPKG) app-shells/dash; \
Baselayout-2/openrc compatibility and stage4 tarballs. The first major change here is the support of baselayout-2/openrc. So far Gentoo has not released a stage3 tarball with baselayout-2, but I've tested this enough that I feel it works even when doing an upgrade. The baselayout-1 stuff has been converted, however it is recommended to not use this until baselayout-2 is available in Gentoo stage3s as I don't want to support converting, or you can do this: stage4 tarball support. I'm not sure why I didn't support this before. Now not only can stage4 tarballs be build, instead of or in addition to virtual appliance images, but stage4 tarballs can also be used in lieu of a stage3. There is a new "stage4" make target, and also when building the Makefile will first look for stage4/<appliance>-stage4.tar.bz2 and if that exists use it instead of the Gentoo stage3. If you specify stage4 as a target and also already have a stage4, then the Makefile will unpack the stage4 into the chroot, perform updates, and then re-create the stage4 based on the updates (atomically). In addition there is a new Makefile variable, SOFTWARE. The default value is "1" meaning it will call the software target (thereby installing/updatein software), but if you set SOFTWARE=0, then the software phase will not be run. This can allow, for example, to build a VM image from a stage4 without performing software updates, in effect a straight stage4 to image for quick image building. Since most appliances are pretty much based on the "base" appliance, one could imply copy the base stage4 to the new appliance stage4 and start from there, instead of having to start from a vanilla stage3, for example: # cp stage4/base-stage4.tar.bz2 stage4/kde-stage4.tar.bz2 # make APPLIANCE=kde stage4 Will take the already existing base stage4 and simply update it to kde, which will be easier/faster than starting from a stage3. There are still some tweaks that need to be done for the stage4 support. Specifically Makefile targets need to be written with the assumption that they may be called more than once (e.g. updating a stage4 or going from stage4 to image with SOFTWARE=1). For the most part things work according to that assumption, but there are a few things that need to be tweeked, such as the inittab settings if one is building a "headed" image but it's based off a headless stage4. New appliance authors should also write their "preinstall" and "postinstall" targets with the assmption that it may be called more than once.
2011-05-18 02:44:04 +02:00
echo /bin/dash >> $(CHROOT)/etc/shells; \
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
RUN chsh -s /bin/sh root; \
Baselayout-2/openrc compatibility and stage4 tarballs. The first major change here is the support of baselayout-2/openrc. So far Gentoo has not released a stage3 tarball with baselayout-2, but I've tested this enough that I feel it works even when doing an upgrade. The baselayout-1 stuff has been converted, however it is recommended to not use this until baselayout-2 is available in Gentoo stage3s as I don't want to support converting, or you can do this: stage4 tarball support. I'm not sure why I didn't support this before. Now not only can stage4 tarballs be build, instead of or in addition to virtual appliance images, but stage4 tarballs can also be used in lieu of a stage3. There is a new "stage4" make target, and also when building the Makefile will first look for stage4/<appliance>-stage4.tar.bz2 and if that exists use it instead of the Gentoo stage3. If you specify stage4 as a target and also already have a stage4, then the Makefile will unpack the stage4 into the chroot, perform updates, and then re-create the stage4 based on the updates (atomically). In addition there is a new Makefile variable, SOFTWARE. The default value is "1" meaning it will call the software target (thereby installing/updatein software), but if you set SOFTWARE=0, then the software phase will not be run. This can allow, for example, to build a VM image from a stage4 without performing software updates, in effect a straight stage4 to image for quick image building. Since most appliances are pretty much based on the "base" appliance, one could imply copy the base stage4 to the new appliance stage4 and start from there, instead of having to start from a vanilla stage3, for example: # cp stage4/base-stage4.tar.bz2 stage4/kde-stage4.tar.bz2 # make APPLIANCE=kde stage4 Will take the already existing base stage4 and simply update it to kde, which will be easier/faster than starting from a stage3. There are still some tweaks that need to be done for the stage4 support. Specifically Makefile targets need to be written with the assumption that they may be called more than once (e.g. updating a stage4 or going from stage4 to image with SOFTWARE=1). For the most part things work according to that assumption, but there are a few things that need to be tweeked, such as the inittab settings if one is building a "headed" image but it's based off a headless stage4. New appliance authors should also write their "preinstall" and "postinstall" targets with the assmption that it may be called more than once.
2011-05-18 02:44:04 +02:00
fi
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
RUN ln -sf dash /bin/sh
* kernel: Don't pass "-n" to emerge when emerging the kernel as stage4s don't have the kernel sources and subsequent builds will fail * kernel: Remove any old kernel and modules before installing new * Don't link /bin/sh to dash if DASH != YES * Add appliance name and creation date comments to package list files
2011-06-27 12:43:59 +02:00
endif
Makefile: Make the systools target inside the chroot
2015-02-27 23:25:56 +01:00
touch $(SYSTOOLS)
Cleaned up Makefile and hopefully made it more modular. Added preinstall and postinstall scripts for additional software
2010-07-10 20:04:04 +02:00
switch over to GRUB 2 The GRUB 1 configuration hasn't been working in a while and-- let's face it-- it's time. So now we have GRUB 2. It should still work with a serial console though I haven't tested it yet.
2017-05-28 00:13:01 +02:00
$(GRUB): $(PREPROOT) configs/grub.cfg $(KERNEL) scripts/grub-headless.sed
New Makefile variable: EXTERNAL_KERNEL If set to YES, then the kernel sources will not be installed and a kernel is not built, nor is grub installed/configured. This is can be useful when building appliances for hypervisors such as Xen and Qemu/KVM which can run from external kernel/initramfs configurations. Default is NO
2011-02-05 06:06:23 +01:00
ifneq ($(EXTERNAL_KERNEL),YES)
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Installing Grub
A couple more cp/COPY $(inroot)/RUN replacements
2018-10-27 20:25:29 +02:00
RUN $(EMERGE) -nN $(USEPKG) sys-boot/grub
switch over to GRUB 2 The GRUB 1 configuration hasn't been working in a while and-- let's face it-- it's time. So now we have GRUB 2. It should still work with a serial console though I haven't tested it yet.
2017-05-28 00:13:01 +02:00
mkdir -p $(CHROOT)/boot/grub
A couple more cp/COPY $(inroot)/RUN replacements
2018-10-27 20:25:29 +02:00
COPY configs/grub.cfg /boot/grub/grub.cfg
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
ifeq ($(VIRTIO),YES)
switch over to GRUB 2 The GRUB 1 configuration hasn't been working in a while and-- let's face it-- it's time. So now we have GRUB 2. It should still work with a serial console though I haven't tested it yet.
2017-05-28 00:13:01 +02:00
sed -i 's/sda/vda/' $(CHROOT)/boot/grub/grub.cfg
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
endif
ifeq ($(HEADLESS),YES)
switch over to GRUB 2 The GRUB 1 configuration hasn't been working in a while and-- let's face it-- it's time. So now we have GRUB 2. It should still work with a serial console though I haven't tested it yet.
2017-05-28 00:13:01 +02:00
sed -i -f scripts/grub-headless.sed $(CHROOT)/boot/grub/grub.cfg
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
endif
New Makefile variable: EXTERNAL_KERNEL If set to YES, then the kernel sources will not be installed and a kernel is not built, nor is grub installed/configured. This is can be useful when building appliances for hypervisors such as Xen and Qemu/KVM which can run from external kernel/initramfs configurations. Default is NO
2011-02-05 06:06:23 +01:00
endif
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
ln -nsf /run/systemd/resolve/resolv.conf $(CHROOT)/etc/resolv.conf
Makefile: Make the grub target inside the chroot
2015-02-27 22:35:15 +01:00
touch $(GRUB)
Initial commit
2010-07-09 05:22:37 +02:00
Numerous updates: * Exclude some files from the stage3 tarball to be installed in the chroot. This reduces the number of etc-updates that need to be process. * Manually eselect profile. This is needed now because /etc/portage/make.profile is excluded above. * Use m4 and a template (in file) to create /etc/fstab instead of using sed. * Add a "software" target. This is mainly used for development.
2018-12-09 01:12:33 +01:00
software: $(SOFTWARE)
Makefile: Get rid of BUILD_SOFTWARE option. It's hardly useful anymore.
2015-03-01 02:31:55 +01:00
Numerous updates: * Exclude some files from the stage3 tarball to be installed in the chroot. This reduces the number of etc-updates that need to be process. * Manually eselect profile. This is needed now because /etc/portage/make.profile is excluded above. * Use m4 and a template (in file) to create /etc/fstab instead of using sed. * Add a "software" target. This is mainly used for development.
2018-12-09 01:12:33 +01:00
$(SOFTWARE): $(SYSTOOLS) configs/eth.network configs/issue $(COMPILE_OPTIONS) $(WORLD)
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Building $(APPLIANCE)-specific software
allowing the use of a default appliance An appliance with the name "default" can be created, and its configuration is used as the basis for all other appliances.
2021-02-07 18:31:01 +01:00
if test -f appliances/default/Makefile; \
then $(MAKE) -C appliances/default preinstall; \
fi
Move appliances/configs/scripts to seperate directories. Instead of having everything in the root directory, split them in seperate directories (appliances, scripts, & configs). This makes things a little tidier. Also added a now Makefile target, appliance-list, that prints a list of the available appliances. The split directory change made this easier.
2014-06-09 04:26:17 +02:00
$(MAKE) -C appliances/$(APPLIANCE) preinstall
* Pre-emerge xz-utils as some packages need this to unpack * Clean up Makefile a little
2010-11-06 22:49:19 +01:00
allowing the use of a default appliance An appliance with the name "default" can be created, and its configuration is used as the basis for all other appliances.
2021-02-07 18:31:01 +01:00
if test -f $(WORLD_DEFAULT); \
builds the kernel separately to avoid having to rebuild it for any appliance
2021-05-22 19:53:34 +02:00
then cat $(WORLD_DEFAULT) >> $(CHROOT)/var/lib/portage/world; \
allowing the use of a default appliance An appliance with the name "default" can be created, and its configuration is used as the basis for all other appliances.
2021-02-07 18:31:01 +01:00
fi
cat $(WORLD) >> $(CHROOT)/var/lib/portage/world
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
RUN $(EMERGE) $(USEPKG) --update --newuse --deep @system
* Pre-emerge xz-utils as some packages need this to unpack * Clean up Makefile a little
2010-11-06 22:49:19 +01:00
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Running @preserved-rebuild
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
RUN $(EMERGE) --usepkg=n @preserved-rebuild
* Pre-emerge xz-utils as some packages need this to unpack * Clean up Makefile a little
2010-11-06 22:49:19 +01:00
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
COPY configs/issue /etc/issue
RUN $(EMERGE) $(USEPKG) --update --newuse --deep @world $(grub_package)
RUN $(EMERGE) --depclean --with-bdeps=n
RUN --setenv EDITOR=/usr/bin/nano etc-update
COPY configs/eth.network /etc/systemd/network/eth.network
RUN systemctl enable systemd-networkd.service
RUN systemctl enable systemd-resolved.service
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
ifeq ($(ENABLE_SSHD),YES)
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
RUN systemctl enable sshd.service
* Move all the kernel-building logic to a seperate shell script * Make the Makefile less ugly and embarrassing (I hope) * Remove the stage3 devnode fix as the latest stage3s appear fixed
2011-06-29 06:43:12 +02:00
endif
Fix problem where kernel.sh wasn't actually building a new kernel.
2011-07-18 00:10:57 +02:00
ifeq ($(DASH),YES)
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
RUN $(EMERGE) --depclean app-shells/bash
Fix problem where kernel.sh wasn't actually building a new kernel.
2011-07-18 00:10:57 +02:00
endif
allowing the use of a default appliance An appliance with the name "default" can be created, and its configuration is used as the basis for all other appliances.
2021-02-07 18:31:01 +01:00
if test -f appliances/default/Makefile; \
then $(MAKE) -C appliances/default postinstall; \
fi
Makefile: run "postinstall" as late as possible This is in case the "postinstall" step wants to override something that the software target did.
2016-12-06 03:32:58 +01:00
$(MAKE) -C appliances/$(APPLIANCE) postinstall
* New Makefile variable PKGLIST. When set to 1 will create a file outside the appliance with the list of installed packages on that appliance. PKGLIST is off by default. * Works with baselayout-2 stage3s, including the fix for the current broken stage3 tarballs. * The new stage3 tarballs are much more limited as far as what dev nodes are included. In addition to being broken stage3s themselves, it also broke the UDEV=NO option. So I have included my own device node tarball which is installed when UDEV=NO. * Put double quotes around hostname in /etc/conf.d/hostname.
2011-06-23 03:42:59 +02:00
ifneq ($(PKGLIST),0)
* kernel: Don't pass "-n" to emerge when emerging the kernel as stage4s don't have the kernel sources and subsequent builds will fail * kernel: Remove any old kernel and modules before installing new * Don't link /bin/sh to dash if DASH != YES * Add appliance name and creation date comments to package list files
2011-06-27 12:43:59 +02:00
echo \# > $(LST_FILE)
echo \# Gentoo Virtual Appliance \"$(APPLIANCE)\" package list >> $(LST_FILE)
echo \# Generated `date -u` >> $(LST_FILE)
echo \# >> $(LST_FILE)
Exclude virtuals from the package list file There's really no point in showing the virtuals.
2015-09-03 16:11:01 +02:00
(cd "$(CHROOT)"/var/db/pkg ; /bin/ls -1d */* | grep -v '^virtual/') >> $(LST_FILE)
* New Makefile variable PKGLIST. When set to 1 will create a file outside the appliance with the list of installed packages on that appliance. PKGLIST is off by default. * Works with baselayout-2 stage3s, including the fix for the current broken stage3 tarballs. * The new stage3 tarballs are much more limited as far as what dev nodes are included. In addition to being broken stage3s themselves, it also broke the UDEV=NO option. So I have included my own device node tarball which is installed when UDEV=NO. * Put double quotes around hostname in /etc/conf.d/hostname.
2011-06-23 03:42:59 +02:00
endif
Makefile: Make the software target inside the chroot
2015-02-27 22:46:57 +01:00
touch $(SOFTWARE)
Initial commit
2010-07-09 05:22:37 +02:00
Makefile: make the $(RAW_IMAGE) target install the stage4 files. The raw image making was kind of split up, with different targets to create the image, partition, copy files, install grub, etc. This change makes it all one target. After "make image" is done, or, e.g., "make images/base.img" then the resulting file will be built and contain all the necessary files. This make the $(RAW_IMAGE) target more uniform with the other image/ targets. It will also make the other image/ targets easier to satify.
2015-02-28 23:27:39 +01:00
$(RAW_IMAGE): $(STAGE4_TARBALL) scripts/grub.shell scripts/motd.sh
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Installing files to `basename $(RAW_IMAGE)`
Makefile: make the $(RAW_IMAGE) target install the stage4 files. The raw image making was kind of split up, with different targets to create the image, partition, copy files, install grub, etc. This change makes it all one target. After "make image" is done, or, e.g., "make images/base.img" then the resulting file will be built and contain all the necessary files. This make the $(RAW_IMAGE) target more uniform with the other image/ targets. It will also make the other image/ targets easier to satify.
2015-02-28 23:27:39 +01:00
qemu-img create -f raw $(RAW_IMAGE).tmp $(DISK_SIZE)
switch over to GRUB 2 The GRUB 1 configuration hasn't been working in a while and-- let's face it-- it's time. So now we have GRUB 2. It should still work with a serial console though I haven't tested it yet.
2017-05-28 00:13:01 +02:00
parted -s $(RAW_IMAGE).tmp mklabel msdos
Makefile: make the $(RAW_IMAGE) target install the stage4 files. The raw image making was kind of split up, with different targets to create the image, partition, copy files, install grub, etc. This change makes it all one target. After "make image" is done, or, e.g., "make images/base.img" then the resulting file will be built and contain all the necessary files. This make the $(RAW_IMAGE) target more uniform with the other image/ targets. It will also make the other image/ targets easier to satify.
2015-02-28 23:27:39 +01:00
parted -s $(RAW_IMAGE).tmp mkpart primary 1 $(DISK_SIZE)
parted -s $(RAW_IMAGE).tmp set 1 boot on
sync
losetup --show --find --partscan $(RAW_IMAGE).tmp > partitions
use labels to create fstab use swap partition if available update python (3.11) fix fetching stage3
2023-06-02 18:02:49 +02:00
mkfs.ext4 -O sparse_super,^has_journal -L ROOT -m 0 `cat partitions`p1
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
mkdir $(CHROOT)
mount -o noatime `cat partitions`p1 $(CHROOT)
tar -xf $(STAGE4_TARBALL) --numeric-owner $(COPY_ARGS) -C $(CHROOT)
Makefile: remove scripts/ as it is now in PATH
2018-10-27 20:54:21 +02:00
motd.sh $(EXTERNAL_KERNEL) $(VIRTIO) $(DISK_SIZE) $(SWAP_SIZE) $(DASH) $(VA_ARCH) > $(CHROOT)/etc/motd
New Makefile variable: EXTERNAL_KERNEL If set to YES, then the kernel sources will not be installed and a kernel is not built, nor is grub installed/configured. This is can be useful when building appliances for hypervisors such as Xen and Qemu/KVM which can run from external kernel/initramfs configurations. Default is NO
2011-02-05 06:06:23 +01:00
ifneq ($(EXTERNAL_KERNEL),YES)
- Adjustments to current Gentoo changes - Adjustments to create the appliance on Debian - use grub-install from appliance (not from build host) - fixes
2024-04-15 09:45:56 +02:00
echo '(hd0) ' `cat partitions` > $(CHROOT)/device-map
cp partitions $(CHROOT)/partitions
RUN /usr/sbin/grub-install --no-floppy --grub-mkdevicemap=device-map --directory=/usr/lib/grub/i386-pc --boot-directory=/boot `cat partitions`
rm $(CHROOT)/device-map $(CHROOT)/partitions
New Makefile variable: EXTERNAL_KERNEL If set to YES, then the kernel sources will not be installed and a kernel is not built, nor is grub installed/configured. This is can be useful when building appliances for hypervisors such as Xen and Qemu/KVM which can run from external kernel/initramfs configurations. Default is NO
2011-02-05 06:06:23 +01:00
endif
Makefile: make the $(RAW_IMAGE) target install the stage4 files. The raw image making was kind of split up, with different targets to create the image, partition, copy files, install grub, etc. This change makes it all one target. After "make image" is done, or, e.g., "make images/base.img" then the resulting file will be built and contain all the necessary files. This make the $(RAW_IMAGE) target more uniform with the other image/ targets. It will also make the other image/ targets easier to satify.
2015-02-28 23:27:39 +01:00
umount $(CHROOT)
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
rmdir $(CHROOT)
Makefile: use losetup instead of qemu-nbd for loop mounting. It's more dynamic, is faster, and the newer versions support auto-creating device nodes for partions. So it's prefereable to qemu-nbd.
2014-06-11 17:59:57 +02:00
sync
losetup --detach `cat partitions`
Makefile: image, stage4: clean up after oneself Make these targets that have temporary targets/mount-points clean up after themselves.
2014-08-30 20:12:04 +02:00
rm -f partitions device-map
Makefile: make the $(RAW_IMAGE) target install the stage4 files. The raw image making was kind of split up, with different targets to create the image, partition, copy files, install grub, etc. This change makes it all one target. After "make image" is done, or, e.g., "make images/base.img" then the resulting file will be built and contain all the necessary files. This make the $(RAW_IMAGE) target more uniform with the other image/ targets. It will also make the other image/ targets easier to satify.
2015-02-28 23:27:39 +01:00
mv $(RAW_IMAGE).tmp $(RAW_IMAGE)
Initial commit
2010-07-09 05:22:37 +02:00
Make the other image/ targets depend on $(RAW_IMAGE). Instead of "image" so that if the raw image is built and up-to-date then it need not be rebuilt to satisfy the other image targets. This excludes the stage4 "image" which of course is necessary to build the $(RAW_IMAGE) target.
2015-02-28 23:30:01 +01:00
$(QCOW_IMAGE): $(RAW_IMAGE)
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Creating `basename $(QCOW_IMAGE)`
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
qemu-img convert -f raw -O qcow2 -c $(RAW_IMAGE) $(QCOW_IMAGE).tmp
mv $(QCOW_IMAGE).tmp $(QCOW_IMAGE)
Initial commit
2010-07-09 05:22:37 +02:00
qcow: $(QCOW_IMAGE)
Make the other image/ targets depend on $(RAW_IMAGE). Instead of "image" so that if the raw image is built and up-to-date then it need not be rebuilt to satisfy the other image targets. This excludes the stage4 "image" which of course is necessary to build the $(RAW_IMAGE) target.
2015-02-28 23:30:01 +01:00
$(XVA_IMAGE): $(RAW_IMAGE)
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Creating `basename $(XVA_IMAGE)`
Add preliminary support for Xen Virtual Appliance (xva) images.
2011-06-23 15:09:41 +02:00
xva.py --disk=$(RAW_IMAGE) --is-hvm --memory=256 --vcpus=1 --name=$(APPLIANCE) \
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
--filename=$(XVA_IMAGE).tmp
mv $(XVA_IMAGE).tmp $(XVA_IMAGE)
Add preliminary support for Xen Virtual Appliance (xva) images.
2011-06-23 15:09:41 +02:00
xva: $(XVA_IMAGE)
Initial commit
2010-07-09 05:22:37 +02:00
Make the other image/ targets depend on $(RAW_IMAGE). Instead of "image" so that if the raw image is built and up-to-date then it need not be rebuilt to satisfy the other image targets. This excludes the stage4 "image" which of course is necessary to build the $(RAW_IMAGE) target.
2015-02-28 23:30:01 +01:00
$(VMDK_IMAGE): $(RAW_IMAGE)
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Creating `basename $(VMDK_IMAGE)`
allow switching between vmdk images with IDE or SCSI controller
2021-02-05 16:35:27 +01:00
ifeq ($(VMDK_TYPE),SCSI)
- Adjustments to current Gentoo changes - Adjustments to create the appliance on Debian - use grub-install from appliance (not from build host) - fixes
2024-04-15 09:45:56 +02:00
qemu-img convert -f raw -O vmdk -o adapter_type=lsilogic,subformat=streamOptimized,hwversion=7 $(RAW_IMAGE) $(VMDK_IMAGE).tmp
allow switching between vmdk images with IDE or SCSI controller
2021-02-05 16:35:27 +01:00
else
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
qemu-img convert -f raw -O vmdk $(RAW_IMAGE) $(VMDK_IMAGE).tmp
allow switching between vmdk images with IDE or SCSI controller
2021-02-05 16:35:27 +01:00
endif
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
mv $(VMDK_IMAGE).tmp $(VMDK_IMAGE)
Initial commit
2010-07-09 05:22:37 +02:00
vmdk: $(VMDK_IMAGE)
allow the creation of ova images requires open-vmdk, a gentoo ebuild is available here: https://git.unitas-network.de/Gentoo/unitas-misc/src/branch/master/app-emulation/open-vmdk
2021-02-05 16:41:23 +01:00
NUM_CPUS := $(OVA_NUM_CPUS)
MEM_SIZE := $(OVA_MEM_SIZE)
export NUM_CPUS MEM_SIZE
$(OVA_IMAGE): $(VMDK_IMAGE)
@print Creating `basename $(OVA_IMAGE)`
- Adjustments to current Gentoo changes - Adjustments to create the appliance on Debian - use grub-install from appliance (not from build host) - fixes
2024-04-15 09:45:56 +02:00
cd $(IMAGES) && mkova.sh $(APPLIANCE) /usr/share/open-vmdk/template-hw7.ovf $(VMDK_IMAGE)
allow the creation of ova images requires open-vmdk, a gentoo ebuild is available here: https://git.unitas-network.de/Gentoo/unitas-misc/src/branch/master/app-emulation/open-vmdk
2021-02-05 16:41:23 +01:00
ova: $(OVA_IMAGE)
stage3 tarball is now an xz archive
2021-02-05 12:27:13 +01:00
$(STAGE4_TARBALL): $(PORTAGE_DIR) stage3-$(VA_ARCH).tar.xz appliances/$(APPLIANCE) configs/rsync-excludes
stage4: Remove "build_stage4" and don't force stage4 to build every time The stage4 target, specifically the STAGE4_TARBALL target now depends on the portage/ directory, the appliances/<appliance>/ directory and the stage3 tarball. It will not be rebuild if these are up-to-date. Therefore other targets that depend on stage4 (e.g. RAW_IMAGE) won't force stage4 to be rebuilt if it is up to date. If you want to force a stage4 rebuild, for example if the appliance pulls from a live VCS, then the recommended way to do this is: $ touch appliances/<appliance> $ make APPLIANCE=<appliance> stage4
2015-02-28 23:35:45 +01:00
$(MAKE) $(STAGE3)
$(MAKE) $(PREPROOT)
$(MAKE) $(SOFTWARE)
$(MAKE) $(KERNEL)
$(MAKE) $(GRUB)
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Creating stage4 tarball: `basename $(STAGE4_TARBALL)`
Makefile: perform the change-password step in the stage4 phase This should really happen as late as possibly and possibly not at all. If we change (lock) the password too soon, then some build steps can fail. For example, adduser will fail if root needs to change its password first.
2016-12-08 12:57:41 +01:00
$(change_password)
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
mkdir -p $(IMAGES)
tar -acf "$(STAGE4_TARBALL).tmp.xz" --numeric-owner $(COPY_ARGS) -C $(CHROOT) --one-file-system .
Use xz compression for stage4 tarballs. * And remove dud stage4 removal in "clean" target.
2012-11-15 14:30:30 +01:00
mv "$(STAGE4_TARBALL).tmp.xz" "$(STAGE4_TARBALL)"
stage4: Remove "build_stage4" and don't force stage4 to build every time The stage4 target, specifically the STAGE4_TARBALL target now depends on the portage/ directory, the appliances/<appliance>/ directory and the stage3 tarball. It will not be rebuild if these are up-to-date. Therefore other targets that depend on stage4 (e.g. RAW_IMAGE) won't force stage4 to be rebuilt if it is up to date. If you want to force a stage4 rebuild, for example if the appliance pulls from a live VCS, then the recommended way to do this is: $ touch appliances/<appliance> $ make APPLIANCE=<appliance> stage4
2015-02-28 23:35:45 +01:00
$(MAKE) clean
Baselayout-2/openrc compatibility and stage4 tarballs. The first major change here is the support of baselayout-2/openrc. So far Gentoo has not released a stage3 tarball with baselayout-2, but I've tested this enough that I feel it works even when doing an upgrade. The baselayout-1 stuff has been converted, however it is recommended to not use this until baselayout-2 is available in Gentoo stage3s as I don't want to support converting, or you can do this: stage4 tarball support. I'm not sure why I didn't support this before. Now not only can stage4 tarballs be build, instead of or in addition to virtual appliance images, but stage4 tarballs can also be used in lieu of a stage3. There is a new "stage4" make target, and also when building the Makefile will first look for stage4/<appliance>-stage4.tar.bz2 and if that exists use it instead of the Gentoo stage3. If you specify stage4 as a target and also already have a stage4, then the Makefile will unpack the stage4 into the chroot, perform updates, and then re-create the stage4 based on the updates (atomically). In addition there is a new Makefile variable, SOFTWARE. The default value is "1" meaning it will call the software target (thereby installing/updatein software), but if you set SOFTWARE=0, then the software phase will not be run. This can allow, for example, to build a VM image from a stage4 without performing software updates, in effect a straight stage4 to image for quick image building. Since most appliances are pretty much based on the "base" appliance, one could imply copy the base stage4 to the new appliance stage4 and start from there, instead of having to start from a vanilla stage3, for example: # cp stage4/base-stage4.tar.bz2 stage4/kde-stage4.tar.bz2 # make APPLIANCE=kde stage4 Will take the already existing base stage4 and simply update it to kde, which will be easier/faster than starting from a stage3. There are still some tweaks that need to be done for the stage4 support. Specifically Makefile targets need to be written with the assumption that they may be called more than once (e.g. updating a stage4 or going from stage4 to image with SOFTWARE=1). For the most part things work according to that assumption, but there are a few things that need to be tweeked, such as the inittab settings if one is building a "headed" image but it's based off a headless stage4. New appliance authors should also write their "preinstall" and "postinstall" targets with the assmption that it may be called more than once.
2011-05-18 02:44:04 +02:00
stage4: Remove "build_stage4" and don't force stage4 to build every time The stage4 target, specifically the STAGE4_TARBALL target now depends on the portage/ directory, the appliances/<appliance>/ directory and the stage3 tarball. It will not be rebuild if these are up-to-date. Therefore other targets that depend on stage4 (e.g. RAW_IMAGE) won't force stage4 to be rebuilt if it is up to date. If you want to force a stage4 rebuild, for example if the appliance pulls from a live VCS, then the recommended way to do this is: $ touch appliances/<appliance> $ make APPLIANCE=<appliance> stage4
2015-02-28 23:35:45 +01:00
stage4: $(STAGE4_TARBALL)
Baselayout-2/openrc compatibility and stage4 tarballs. The first major change here is the support of baselayout-2/openrc. So far Gentoo has not released a stage3 tarball with baselayout-2, but I've tested this enough that I feel it works even when doing an upgrade. The baselayout-1 stuff has been converted, however it is recommended to not use this until baselayout-2 is available in Gentoo stage3s as I don't want to support converting, or you can do this: stage4 tarball support. I'm not sure why I didn't support this before. Now not only can stage4 tarballs be build, instead of or in addition to virtual appliance images, but stage4 tarballs can also be used in lieu of a stage3. There is a new "stage4" make target, and also when building the Makefile will first look for stage4/<appliance>-stage4.tar.bz2 and if that exists use it instead of the Gentoo stage3. If you specify stage4 as a target and also already have a stage4, then the Makefile will unpack the stage4 into the chroot, perform updates, and then re-create the stage4 based on the updates (atomically). In addition there is a new Makefile variable, SOFTWARE. The default value is "1" meaning it will call the software target (thereby installing/updatein software), but if you set SOFTWARE=0, then the software phase will not be run. This can allow, for example, to build a VM image from a stage4 without performing software updates, in effect a straight stage4 to image for quick image building. Since most appliances are pretty much based on the "base" appliance, one could imply copy the base stage4 to the new appliance stage4 and start from there, instead of having to start from a vanilla stage3, for example: # cp stage4/base-stage4.tar.bz2 stage4/kde-stage4.tar.bz2 # make APPLIANCE=kde stage4 Will take the already existing base stage4 and simply update it to kde, which will be easier/faster than starting from a stage3. There are still some tweaks that need to be done for the stage4 support. Specifically Makefile targets need to be written with the assumption that they may be called more than once (e.g. updating a stage4 or going from stage4 to image with SOFTWARE=1). For the most part things work according to that assumption, but there are a few things that need to be tweeked, such as the inittab settings if one is building a "headed" image but it's based off a headless stage4. New appliance authors should also write their "preinstall" and "postinstall" targets with the assmption that it may be called more than once.
2011-05-18 02:44:04 +02:00
Makefile: build compile_options inside the chroot
2015-02-27 21:44:52 +01:00
eclean: $(COMPILE_OPTIONS)
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
RUN $(EMERGE) $(USEPKG) --oneshot --noreplace app-portage/gentoolkit
RUN eclean-pkg
RUN eclean-dist
RUN $(EMERGE) --depclean app-portage/gentoolkit
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
$(MAKE) clean
Initial commit
2010-07-09 05:22:37 +02:00
Various fixes
2010-11-06 09:41:15 +01:00
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
clean:
Makefile: fix a typo "IMAGES" was misspelled.
2015-03-15 13:56:18 +01:00
rm -f partitions device-map $(IMAGES)/*.tmp
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
rm -rf --one-file-system -- $(CHROOT)
Initial commit
2010-07-09 05:22:37 +02:00
realclean: clean
I learned a lot about Makefiles :D So, basically I re-architeched things a bit: The appliance/Makefile.inc fiels are now appliance/Makefile (again). The main Makefile will call "make -C appliance preinstall" and "postinstall" (and in future "clean"). So I got rid of the ugly make variables/include thing. Some of the main Makefile's variables are exported to the sub-makes. Appliances don't really need $(APPLIANCE) anymore as the appliance directory is their CWD. Added some new targets and smarter targets. I can do more with this, but it's a big improvment from last time. Still learning a lot of Makefile magic (been reading other people's Makefiles). Verified that "make -j3" works (at least on the base appliance) but will kill your hard drive :D Introduced "profiles" Which are files with variables you want to override. The file will be "include"ed by the main Makefile. For example, I have a file, "local.cfg" that looks like this: --- 8< ----------------------------- CHROOT = /var/scratch/marduk/vabuild HEADLESS = YES PRUNE_CRITICAL = NO VIRTIO = YES TIMEZONE = EST5EDT DISK_SIZE = 60.0G SWAP_SIZE = 48 PKGDIR = /var/scratch/packages NBD_DEV = /dev/nbd8 all: qcow --- 8< ------------------------------ Then, e.g. i can run "make PROFILE=local APPLIANCE=kde". If you don't specify a PROFILE variable, then it will default to the empty string, which means the main Makefile will attempt to include .cfg So, for example i have: $ ln -s local.cfg .cfg $ make APPLIANCE=kde Don't set PROFILE inside your .cfg file (why would you?). Also, if the [pro]file does not exist, the include fails silently. I will put this info in the wiki eventually...
2010-11-14 00:22:18 +01:00
${RM} $(RAW_IMAGE) $(QCOW_IMAGE) $(VMDK_IMAGE)
Move umounting in it's own target and don't ||true it
2010-11-05 13:06:13 +01:00
Should be compatible with 32bit guests
2010-11-06 23:46:07 +01:00
distclean:
The great systemd commit. This change converts the appliances from openrc to systemd. In addition, systemd needs to at least be be installed on the build machine as we now use systemd-nspawn instead of chroot/bind mounts do to the fact that systemd-nspawn is much more robust and lese prone to errors. In addition: * All stage4 tarballs and images are now stored in the images/ directory by default. * A package dir is now required and is set up in the packages/ directory by default. * The portage directory is not unpacked in the chroot every time anymore and is instead bind-mounted from a directory by systemd-nspawn. This is the portage/ directory by default. * In addition there is a distfiles/ directory (by default) which is bind-mounted in the chroot. It does what you'd probably expect. * The Makefile learned new target, eclean, which will run eclean-dist and eclean-pkg to clean out obsolete distfiles and binary packages. * The REMOVE_PORTAGE_TREE option is removed as portage is no longer installed. * The unused/untested PRUNE_CRITICAL functionality has been removed. I have no idea if it worked and if it didn't I didn't want to fix it. * As appliances are always using systemd, UDEV is no longer optional. * Timezones and hostnames are now handled by systemd (systemd-firstboot). * Stage4 tarballs are now directly importable as systemd containers (and probably docker too though I haven't tested that yet). * A number of packages (for example dhcpd, acpid) have been removed from the appliances when systemd provides equivalent functionality. * We no longer override etc-update.conf. There's no reason. * A number of Makefile targets, checkpoints, temp files, etc have been removed as they are no longer needed.
2015-02-22 16:32:16 +01:00
rm -f -- *.qcow *.img *.vmdk
stage3 tarball is now an xz archive
2021-02-05 12:27:13 +01:00
rm -f stage3-*.tar.xz
Don't autosync portage.
2013-08-25 11:24:46 +02:00
rm -f portage-snapshot.tar.bz2
Should be compatible with 32bit guests
2010-11-06 23:46:07 +01:00
Move appliances/configs/scripts to seperate directories. Instead of having everything in the root directory, split them in seperate directories (appliances, scripts, & configs). This makes things a little tidier. Also added a now Makefile target, appliance-list, that prints a list of the available appliances. The split directory change made this easier.
2014-06-09 04:26:17 +02:00
appliance-list:
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print 'Available appliances:'
Makefile: appliance-list: Display appliances in 1 column
2015-03-09 12:20:14 +01:00
@/bin/ls -1 appliances
Move appliances/configs/scripts to seperate directories. Instead of having everything in the root directory, split them in seperate directories (appliances, scripts, & configs). This makes things a little tidier. Also added a now Makefile target, appliance-list, that prints a list of the available appliances. The split directory change made this easier.
2014-06-09 04:26:17 +02:00
Makefile: new target: checksumps Creates a sha256 checksum file in the $(IMAGES) directory.
2015-03-16 03:08:25 +01:00
checksums:
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print Calculating checksums
Change the way we create checksums
2015-09-14 13:09:15 +02:00
$(RM) $(CHECKSUMS)
cd $(IMAGES) && sha256sum --binary * > $(CHECKSUMS).tmp
images: change the way checksums are produced
2015-08-02 20:15:26 +02:00
mv $(CHECKSUMS).tmp $(CHECKSUMS)
Makefile: new target: checksumps Creates a sha256 checksum file in the $(IMAGES) directory.
2015-03-16 03:08:25 +01:00
Makefile: add a "shell" target This will put you at a shell prompt inside the build environment. Why didn't I think of this before?!
2015-12-09 19:15:09 +01:00
shell: $(PREPROOT)
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print 'Entering interactive shell for the $(APPLIANCE) build.'
@print 'Type "exit" or "^D" to leave'
@print
scripts: add COPY and RUN helpers. Makes the Makefile easier to write and the output a little nicer. Inspired by a similar tool ;-)
2018-10-27 20:04:00 +02:00
@RUN
Makefile: shell: make a quieter So that the user can see the instructional messages better.
2016-03-10 21:10:24 +01:00
@rm -f $(CHROOT)/root/.bash_history
Makefile: add a "shell" target This will put you at a shell prompt inside the build environment. Why didn't I think of this before?!
2015-12-09 19:15:09 +01:00
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
help:
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print 'Help targets (this is not a comprehensive list)'
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
@echo
@echo 'sync_portage - Download the latest portage snapshot'
@echo 'sync_stage3 - Download the latest stage3 tarball'
builds the kernel separately to avoid having to rebuild it for any appliance
2021-05-22 19:53:34 +02:00
@echo 'sync_repos - Download/update the repositories (portage overlays)'
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
@echo 'stage4 - Build a stage4 tarball'
@echo 'clean - Unmount chroot and clean directory'
Makefile: Add missing endquote
2015-03-15 13:56:38 +01:00
@echo 'eclean - Clean outdated packages and distfiles'
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
@echo 'realclean - Clean and remove image files'
Makefile: add a "shell" target This will put you at a shell prompt inside the build environment. Why didn't I think of this before?!
2015-12-09 19:15:09 +01:00
@echo 'shell - Enter a shell in the build environment'
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@print 'Images'
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
@echo 'image - Build a raw VM image from stage4'
@echo 'qcow - Build a qcow VM image from a raw image'
@echo 'vmdk - Build a vmdk image from a raw image'
allow the creation of ova images requires open-vmdk, a gentoo ebuild is available here: https://git.unitas-network.de/Gentoo/unitas-misc/src/branch/master/app-emulation/open-vmdk
2021-02-05 16:41:23 +01:00
@echo 'ova - Build a ova image from a vmdk image'
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
@echo 'xva - Build an xva image from a raw image'
Move appliances/configs/scripts to seperate directories. Instead of having everything in the root directory, split them in seperate directories (appliances, scripts, & configs). This makes things a little tidier. Also added a now Makefile target, appliance-list, that prints a list of the available appliances. The split directory change made this easier.
2014-06-09 04:26:17 +02:00
@echo 'appliance-list - List built-in appliances'
@echo 'help - Show this help'
scripts: rename echo to print I don't want to clash with /bin/echo but I want to remove "/scripts" from the Makefile since it's now in the PATH.
2018-10-27 20:43:45 +02:00
@echo 'Variables'
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
@echo 'APPLIANCE= - The appliance to build'
@echo 'HOSTNAME= - Hostname to give appliance'
@echo 'TIMEZONE= - Timezone to set for the appliance'
@echo 'CHROOT= - The directory to build the chroot'
@echo 'DISK_SIZE= - Size of the disk image'
@echo 'SWAP_SIZE= - Size of the swap file'
s/ARCH/VA_ARCH/
2018-10-27 08:24:05 +02:00
@echo 'VA_ARCH= - Architecture to build for (x86 or amd64)'
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
@echo 'VIRTIO=YES - Configure the stage2/image to use virtio'
@echo 'EXTERNAL_KERNEL=YES - Do not build a kernel in the image'
@echo 'HEADLESS=YES - Build a headless (serial console) image.'
@echo 'ENABLE_SSHD=YES - Enable sshd to start automatically in the image'
allow switching between vmdk images with IDE or SCSI controller
2021-02-05 16:35:27 +01:00
@echo 'VMDK_TYPE=IDE - VMDK image type (IDE or SCSI)'
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
@echo
allow switching between vmdk images with IDE or SCSI controller
2021-02-05 16:35:27 +01:00
@print 'Example to build the base appliance'
@echo 'make APPLIANCE=base HEADLESS=YES VIRTIO=YES stage4 qcow clean'
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
use labels to create fstab use swap partition if available update python (3.11) fix fetching stage3
2023-06-02 18:02:49 +02:00
.PHONY: qcow vmdk ova clean realclean distclean stage4 image stage4 help appliance-list eclean sync_portage sync_stage3 checksums fstab