Init scripts have been refactored to improve readability. The most
important aspect of this refactor is that automated testing has been
implemented using Qemu. Eventually we will get to the point of
automatically building new archzfs packages as soon as a new kernel is
released to the arch testing repo, after that the tests will be used to
determine if the archzfs packages can be pushed out to aur and
archzfs.com.
Closes#22Closes#31Closes#38Closes#48
Add --with-linux-obj flag to configure to prevent the following error:
checking kernel source directory... /usr/lib/modules/4.4.15-1-lts/build
checking kernel build directory... /usr/lib/modules/4.6.3-1-ARCH/build
checking kernel source version... Not found
configure: error: *** Cannot find UTS_RELEASE definition.
Packages built just for the archiso, included in the archzfs main repo.
To install, users will only need to install the archzfs-archiso-linux
package group.
NOTE: This will not work with the default clean-chroot-manager as the
required kernel packages for archiso cannot be installed in the clean
chroot working copy because they are out-of-date. The following change
was made to ccm64 to build the archiso packages:
PACKAGER=$PACKAGER THREADS=$THREADS nice -19 /usr/bin/makechrootpkg -I "/var/cache/pacman/pkg/linux-4.5.4-1-x86_64.pkg.tar.xz" -I "/var/cache/pacman/pkg/linux-headers-4.5.4-1-x86_64.pkg.tar.xz" -c -u -r $CHROOTPATH64
A request has been made upstream to pass -I to makechrootpkg so that
this change no longer requires a custom ccm64 script.