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

385 lines
12 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
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
CHROOT = $(CURDIR)/build
PKGDIR = $(CURDIR)/packages
DISTDIR = $(CURDIR)/distfiles
PORTAGE_DIR = $(CURDIR)/portage
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)
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
IMAGES = $(CURDIR)/images
RAW_IMAGE = $(IMAGES)/$(APPLIANCE).img
QCOW_IMAGE = $(IMAGES)/$(APPLIANCE).qcow
VMDK_IMAGE = $(IMAGES)/$(APPLIANCE).vmdk
XVA_IMAGE = $(IMAGES)/$(APPLIANCE).xva
LST_FILE = $(IMAGES)/$(APPLIANCE)-packages.lst
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
STAGE3 = $(CHROOT)/tmp/stage3
Makefile: build compile_options inside the chroot
2015-02-27 21:44:52 +01:00
COMPILE_OPTIONS = $(CHROOT)/tmp/compile_options
Makefile: Make the software target inside the chroot
2015-02-27 22:46:57 +01:00
SOFTWARE = $(CHROOT)/tmp/software
Makefile: Make the kernel target inside the chroot
2015-02-27 22:20:43 +01:00
KERNEL = $(CHROOT)/tmp/kernel
Makefile: Make the grub target inside the chroot
2015-02-27 22:35:15 +01:00
GRUB = $(CHROOT)/tmp/grub
Makefile: Make the preproot target inside the chroot
2015-02-27 23:05:17 +01:00
PREPROOT = $(CHROOT)/tmp/preproot
Makefile: Make the sysconfig target inside the chroot
2015-02-27 23:12:46 +01:00
SYSCONFIG = $(CHROOT)/tmp/sysconfig
Makefile: Make the systools target inside the chroot
2015-02-27 23:25:56 +01:00
SYSTOOLS = $(CHROOT)/tmp/systools
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
STAGE4_TARBALL = $(CURDIR)/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
ARCH = amd64
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
KERNEL_CONFIG = configs/kernel.config.$(ARCH)
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
Makefile: Make the software target inside the chroot
2015-02-27 22:46:57 +01:00
BUILD_SOFTWARE = 1
* 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
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
ACCEPT_KEYWORDS = amd64
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
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: various updates
2012-05-25 18:33:40 +02:00
EMERGE = /usr/bin/emerge --jobs=4
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/
Added "Airport" virtual appliance: see https://bitbucket.org/marduk/airport
2012-01-09 22:21:06 +01:00
EMERGE_RSYNC = NO
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
PACKAGE_FILES = $(wildcard appliances/$(APPLIANCE)/package.*)
WORLD = appliances/$(APPLIANCE)/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
* 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
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
-include appliance/$(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
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) \
--machine=$(APPLIANCE)-build \
--bind=$(PORTAGE_DIR):/usr/portage \
--bind=$(PKGDIR):/usr/portage/packages \
--bind=$(DISTDIR):/usr/portage/distfiles
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
ifeq ($(ARCH),x86)
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))
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
software-deps := $(STAGE3)
Makefile: created "inroot" macro for running commands in the chroot
2011-02-25 05:20:38 +01:00
Makefile: Make the software target inside the chroot
2015-02-27 22:46:57 +01:00
ifneq ($(BUILD_SOFTWARE),0)
* 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
software-deps += build-software
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
endif
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
Makefile: created "inroot" macro for running commands in the chroot
2011-02-25 05:20:38 +01:00
change_password = $(inroot) usermod -p '$(ROOT_PASSWORD)' root
New makefile variable, ROOT_PASSWORD, to set the (encrypted) root password
2011-01-12 04:47:14 +01:00
else
Makefile: created "inroot" macro for running commands in the chroot
2011-02-25 05:20:38 +01:00
change_password = $(inroot) passwd -d root; $(inroot) passwd -e 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
Tweaks: * Added UDEV Makefile variable, if set to NO, will disable UDEV and use static /dev (defaults to YES) * Run eselct python to get around "which python am i?" situation * export "inroot" variable
2011-04-02 15:56:19 +02:00
export APPLIANCE ACCEPT_KEYWORDS CHROOT EMERGE HEADLESS M4 M4C inroot
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
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: 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
unexport PKGDIR ARCH
Initial commit
2010-07-09 05:22:37 +02:00
all: 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
image: $(RAW_IMAGE)
Initial commit
2010-07-09 05:22:37 +02:00
Don't autosync portage.
2013-08-25 11:24:46 +02:00
portage-snapshot.tar.bz2:
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
@scripts/echo You do not have a portage snapshot. Consider \"make sync_portage\"
Don't autosync portage.
2013-08-25 11:24:46 +02:00
@exit 1
Small tweak to allow downloading of stage3 and portage in parallel (with -j2)
2011-01-20 03:16:13 +01:00
sync_portage:
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
@scripts/echo Grabbing latest portage snapshot
Don't autosync portage.
2013-08-25 11:24:46 +02:00
rsync --no-motd -L $(RSYNC_MIRROR)/snapshots/portage-latest.tar.bz2 portage-snapshot.tar.bz2
Small tweak to allow downloading of stage3 and portage in parallel (with -j2)
2011-01-20 03:16:13 +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
$(PORTAGE_DIR): portage-snapshot.tar.bz2
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
@scripts/echo Unpacking portage snapshot
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 $(PORTAGE_DIR)
mkdir $(PORTAGE_DIR)
tar xf portage-snapshot.tar.bz2 -C $(PORTAGE_DIR)/..
Added "Airport" virtual appliance: see https://bitbucket.org/marduk/airport
2012-01-09 22:21:06 +01:00
ifeq ($(EMERGE_RSYNC),YES)
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
@scripts/echo Syncing portage tree
Added "Airport" virtual appliance: see https://bitbucket.org/marduk/airport
2012-01-09 22:21:06 +01:00
$(inroot) emerge --sync --quiet
endif
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
Makefile: Make the preproot target inside the chroot
2015-02-27 23:05:17 +01:00
$(PREPROOT): $(STAGE3) $(PORTAGE_DIR) configs/fstab
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 $(PKGDIR) $(DISTDIR)
#$(inroot) sed -i 's/root:.*/root::9797:0:::::/' /etc/shadow
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
cp configs/fstab $(CHROOT)/etc/fstab
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
cp -L /etc/resolv.conf $(CHROOT)/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
Don't autosync the stage3 tarball.
2013-08-26 23:21:17 +02:00
stage3-$(ARCH)-latest.tar.bz2:
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
@scripts/echo 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:
sync_stage3: Use a helper script The Makefile logic was lousy and broken. Add a more robust helper script.
2015-02-16 19:03:44 +01:00
./scripts/sync-stage3.sh $(ARCH)
Don't autosync the stage3 tarball.
2013-08-26 23:21:17 +02:00
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
$(STAGE3): stage3-$(ARCH)-latest.tar.bz2
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
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
@scripts/echo Using stage4 tarball: $(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
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
@scripts/echo Using stage3 tarball
Remove "archiving" options from tar commands. GNU Tar can (usually) handle this automagically
2013-10-13 17:56:20 +02:00
tar xpf stage3-$(ARCH)-latest.tar.bz2 -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
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
Makefile: build compile_options inside the chroot
2015-02-27 21:44:52 +01:00
$(COMPILE_OPTIONS): $(STAGE3) $(PORTAGE_DIR) configs/make.conf.$(ARCH) configs/locale.gen $(PACKAGE_FILES)
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
cp configs/make.conf.$(ARCH) $(CHROOT)/etc/portage/make.conf
Various update to Makefile and make.conf.
2012-12-10 19:13:55 +01:00
echo ACCEPT_KEYWORDS=$(ACCEPT_KEYWORDS) >> $(CHROOT)/etc/portage/make.conf
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
-[ -f "appliances/$(APPLIANCE)/make.conf" ] && cat "appliances/$(APPLIANCE)/make.conf" >> $(CHROOT)/etc/portage/make.conf
Makefile: update to the first profile.
2013-07-22 15:13:55 +02:00
$(inroot) eselect profile set 1
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
cp configs/locale.gen $(CHROOT)/etc/locale.gen
Makefile: created "inroot" macro for running commands in the chroot
2011-02-25 05:20:38 +01:00
$(inroot) locale-gen
Fix package.* files installation to work with new stage3's The new (2015-02) stage3 tarballs use package.* directories instead of files, causing the files to fail to be copied over. This change instead copies them to the directories, creating them if they don't already exist.
2015-02-28 23:20:50 +01:00
for f in $(PACKAGE_FILES); do \
base=`basename $$f` ; \
mkdir -p $(CHROOT)/etc/portage/$$base; \
cp $$f $(CHROOT)/etc/portage/$$base/virtual-appliance-$$base; \
done
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
Makefile: Make the kernel target inside the chroot
2015-02-27 22:20:43 +01:00
$(KERNEL): $(COMPILE_OPTIONS) $(KERNEL_CONFIG) scripts/kernel.sh
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)
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
@scripts/echo Configuring kernel
* 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
cp $(KERNEL_CONFIG) $(CHROOT)/root/kernel.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
cp scripts/kernel.sh $(CHROOT)/root/kernel.sh
Makefile: Make the kernel target inside the chroot
2015-02-27 22:20:43 +01:00
$(inroot) --setenv=KERNEL=$(KERNEL_PKG) \
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
--setenv=EMERGE="$(EMERGE)" \
--setenv=USEPKG="$(USEPKG)" \
--setenv=MAKEOPTS="$(MAKEOPTS)" \
/bin/sh /root/kernel.sh
rm -f $(CHROOT)/root/kernel.sh
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
Makefile: Make the preproot target inside the chroot
2015-02-27 23:05:17 +01:00
$(SWAP_FILE): $(PREPROOT)
Makefile: ALlow for creation of swap-less appliances. Also fix a bug where fstab (and hostname) were not (always) being updated.
2013-09-01 18:06:08 +02:00
ifneq ($(SWAP_SIZE),0)
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
@scripts/echo Creating swap file: $(SWAP_FILE)
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
dd if=/dev/zero of=$(SWAP_FILE) bs=1M count=$(SWAP_SIZE)
/sbin/mkswap $(SWAP_FILE)
Makefile: ALlow for creation of swap-less appliances. Also fix a bug where fstab (and hostname) were not (always) being updated.
2013-09-01 18:06:08 +02:00
else
sed -i '/swap/d' $(CHROOT)/etc/fstab
endif
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 sysconfig target inside the chroot
2015-02-27 23:12:46 +01:00
$(SYSCONFIG): $(PREPROOT) $(SWAP_FILE)
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
@echo $(VIRTIO)
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
ifeq ($(VIRTIO),YES)
* 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
sed -i 's/sda/vda/' $(CHROOT)/etc/fstab
endif
Makefile: Make the sysconfig target inside the chroot
2015-02-27 23:12:46 +01:00
touch $(SYSCONFIG)
Initial commit
2010-07-09 05:22:37 +02:00
Makefile: Make the systools target inside the chroot
2015-02-27 23:25:56 +01:00
$(SYSTOOLS): $(SYSCONFIG) $(COMPILE_OPTIONS)
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
@scripts/echo Installing standard system tools
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) $(EMERGE) --unmerge sys-fs/udev
$(inroot) $(EMERGE) $(USEPKG) -n1 sys-apps/systemd
$(inroot) systemd-firstboot \
--timezone=$(TIMEZONE) \
--hostname=$(HOSTNAME) \
--root-password=
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)"; \
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
then $(inroot) $(EMERGE) -n $(USEPKG) app-shells/dash; \
echo /bin/dash >> $(CHROOT)/etc/shells; \
Use busybox for dhcp and acpi.
2012-12-16 16:49:21 +01:00
$(inroot) 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
$(inroot) 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
Makefile: Make the preproot target inside the chroot
2015-02-27 23:05:17 +01:00
$(GRUB): $(PREPROOT) configs/grub.conf $(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)
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
@scripts/echo Installing Grub
Various update to Makefile and make.conf.
2012-12-10 19:13:55 +01:00
$(inroot) $(EMERGE) -nN $(USEPKG) sys-boot/grub-static
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
cp configs/grub.conf $(CHROOT)/boot/grub/grub.conf
* 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)
sed -i 's/sda/vda/' $(CHROOT)/boot/grub/grub.conf
endif
ifeq ($(HEADLESS),YES)
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
sed -i -f scripts/grub-headless.sed $(CHROOT)/boot/grub/grub.conf
* 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
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) ln -nsf /run/systemd/resolve/resolv.conf /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
Makefile: Make the systools target inside the chroot
2015-02-27 23:25:56 +01:00
build-software: $(SYSTOOLS) configs/eth.network configs/issue $(WORLD)
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
@scripts/echo Building $(APPLIANCE)-specific software
$(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
Makefile: change the way we test if the world file is empty. Use stat(1) instead of catting the file.
2012-12-22 02:05:02 +01:00
if test `stat -c "%s" $(WORLD)` -ne 0 ; then \
Use busybox for dhcp and acpi.
2012-12-16 16:49:21 +01:00
$(inroot) $(EMERGE) $(USEPKG) --update --newuse --deep `cat $(WORLD)` $(EXTRA_WORLD); \
else \
true; \
fi
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
-$(gcc_config)
* Pre-emerge xz-utils as some packages need this to unpack * Clean up Makefile a little
2010-11-06 22:49:19 +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
@scripts/echo Running @preserved-rebuild
$(inroot) $(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
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
cp configs/issue $(CHROOT)/etc/issue
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
-$(gcc_config)
Makefile: created "inroot" macro for running commands in the chroot
2011-02-25 05:20:38 +01:00
$(inroot) $(EMERGE) $(USEPKG) --update --newuse --deep world
$(inroot) $(EMERGE) --depclean --with-bdeps=n
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
-$(gcc_config)
Various update to Makefile and make.conf.
2012-12-10 19:13:55 +01:00
EDITOR=/usr/bin/nano $(inroot) etc-update
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) postinstall
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
cp configs/eth.network $(CHROOT)/etc/systemd/network/eth.network
$(inroot) systemctl enable systemd-networkd.service
$(inroot) 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)
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) 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
Makefile: make changing of root password and removing or portage tree both optional
2010-12-20 05:04:11 +01:00
$(change_password)
Fix problem where kernel.sh wasn't actually building a new kernel.
2011-07-18 00:10:57 +02:00
ifeq ($(DASH),YES)
Use busybox for dhcp and acpi.
2012-12-16 16:49:21 +01:00
$(inroot) $(EMERGE) -c app-shells/bash
Fix problem where kernel.sh wasn't actually building a new kernel.
2011-07-18 00:10:57 +02:00
endif
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: Make the software target inside the chroot
2015-02-27 22:46:57 +01:00
$(SOFTWARE): $(software-deps)
* 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)
(cd "$(CHROOT)"/var/db/pkg ; /bin/ls -1d */*) >> $(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
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
@scripts/echo Installing files to $(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)
parted -s $(RAW_IMAGE).tmp mklabel gpt
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
mkfs.ext4 -O sparse_super,^has_journal -L "$(APPLIANCE)"_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)
scripts/motd.sh $(EXTERNAL_KERNEL) $(VIRTIO) $(DISK_SIZE) $(SWAP_SIZE) $(DASH) $(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)
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
echo '(hd0) ' $(RAW_IMAGE).tmp > device-map
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
$(CHROOT)/sbin/grub --device-map=device-map --no-floppy --batch < scripts/grub.shell
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)
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
@scripts/echo Creating $(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)
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
@scripts/echo Creating $(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)
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
@scripts/echo Creating $(VMDK_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 vmdk $(RAW_IMAGE) $(VMDK_IMAGE).tmp
mv $(VMDK_IMAGE).tmp $(VMDK_IMAGE)
Initial commit
2010-07-09 05:22:37 +02:00
vmdk: $(VMDK_IMAGE)
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_TARBALL): $(PORTAGE) stage3-$(ARCH)-latest.tar.bz2 appliances/$(APPLIANCE) configs/rsync-excludes
$(MAKE) $(STAGE3)
$(MAKE) $(PREPROOT)
$(MAKE) $(SOFTWARE)
$(MAKE) $(KERNEL)
$(MAKE) $(GRUB)
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
@scripts/echo Creating stage4 tarball: $(STAGE4_TARBALL)
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)
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) $(EMERGE) $(USEPKG) -1 --noreplace app-portage/gentoolkit
$(inroot) eclean-pkg
$(inroot) eclean-dist
$(inroot) $(EMERGE) --depclean app-portage/gentoolkit
$(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:
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
Should be compatible with 32bit guests
2010-11-06 23:46:07 +01:00
rm -f latest-stage3.txt stage3-*-latest.tar.bz2
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/echo 'Available appliances:'
@/bin/ls appliances
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
help:
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
@scripts/echo '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'
@echo 'stage4 - Build a stage4 tarball'
@echo 'software - Build software into a chroot'
@echo 'clean - Unmount chroot and clean directory'
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
@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'
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
@scripts/echo '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'
@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/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'
@echo 'ARCH= - Architecture to build for (x86 or amd64)'
@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'
@echo
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
@scripts/echo 'Example'
Makefile: Add a help target.
2013-09-17 01:26:48 +02:00
@echo 'make APPLIANCE=mongodb HEADLESS=YES VIRTIO=YES stage4 qcow clean'
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
.PHONY: qcow vmdk clean realclean distclean stage4 build-software image stage4 help appliance-list eclean sync_portage