You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Jesus Alvarez 231cc988da Only build archiso when necessary 7 years ago
archiso Only build archiso when necessary 7 years ago
packages Update git packages for kernel 4.7.2-1 7 years ago
src initscript refactor and test 7 years ago
testing Only build archiso when necessary 7 years ago
.gitignore Only build archiso when necessary 7 years ago
.gitmodules Add support for archiso packages 7 years ago
README.rst Update readme 8 years ago
TODO.rst initscript refactor and test 7 years ago Add check_internet 7 years ago non-priv user REBASE! 7 years ago Remove check_webpage_retval 7 years ago Fix cd command 7 years ago initscript refactor and test 7 years ago Remove check_webpage_retval 7 years ago Add check_internet 7 years ago
web_archzfs.rst Update webpage with new repo path info 10 years ago


Zettabyte File System for Arch Linux

This project contains the build scripts for archzfs. Two types of packages are
supported, Git packages and LTS packages.

The Git packages include zfs-git, zfs-utils-git, spl-git, and spl-utils-git.
These track the mainline kernel releases in arch. Since Arch is bleeding edge,
so too are these packages. They usually pull from zfsonlinux master branch up
to the latest commit that add supports for latest kernel version.

The LTS packages include zfs-lts, zfs-utils-lts, spl-lts, and spl-utils-lts.
These track the linux-lts packages in arch and are only built using stable
zfsonlinux releases. These packages are the best bet for those concerned with

These packages must be re-built for each kernel release.


The license of the Arch Linux package sources is MIT.

The license of ZFS is CDDL.

The license of SPL is LGPL.


```` uses clean-chroot-manager_ to build packages in a systemd
namespace container.

How to use this Repository

Submitting changes

The Arch User Repository v4 requires package updates to be submitted through
Git. Unfortunately, this makes working with the archzfs build scripts on Github
slightly more complicated. The actual PKGBUILDS in the archzfs repo are set as
git submodules which reference the aur4 git repo and a commit hash. Github does
not support external submodules, and thus PR requests are no longer possible on
PKGBUILDS and mkinitcpio hook scripts.

Contributions are still very much appreciated! To submit a contribution, please
open an issue in Github and within the description post a git generated patch
of the changes. This is only temporary until AUR supports some kind of "pull
request" type system.


.. code:: console

git clone --recursive


1. Set the appropriate variables in

* Repository base path

The parent directory of the ``demz-repo-core`` and ``demz-repo-archiso``

* GPG signing key

Used to sign the packages and repo database.

* Your email address

Used for reporting changes changes in ````. Mutt and msmtp are
used for sending email. Required only if ```` or ````
are going to be used.

* SSH remote login

Used in ```` for making sure the local ``demz-repo-*`` are in
sync with the remote repos.

#. Set the appropriate kernel versions in

#. Update the PKGBUILDs

Use ``./build git update`` to update the archzfs-git PKGBUILDS using the
```` variables.

Use ``./build lts update`` to update the archzfs-lts PKGBUILDS using the
```` variables.

``./ (git|lts) update-test`` uses the ``AZB_LINUX_TEST_*``
variables. Using the test values are useful for test building the zfs
packages against the Linux kernel version in the official testing repo.
Mostly used on minor Linux kernel updates (3.12 -> 3.13).

#. Build the packages

Use ``./ (git|lts) make -u`` to build the packages, update the clean
chroot in the process.

It is possible to use ``./ (git|lts) update make -u`` in one shot.

If you want to see command output only, use ``./ (git|lts) make
-n``. Add the ``-d`` to see debugging output.

#. Add packages to the repo

Use ``./ (git|lts) core -n`` to what changes will occur without
actually making them.

``./ (git|lts) core`` will add the package versions defined by
``AZB_LINUX_VERSION`` to the ``demz-repo-core`` repository.

#. Push the package sources to AUR.

Push to AUR4 using `` (git|lts) aur4``. This commits the latest
changes to each individual package repo (for AUR) and uses ``git push`` to
push to AUR.

.. _clean-chroot-manager: