Initial commit
Merge branch 'newdata' into newbuild

This merge contains a rewrite of build.py to include a class structure to make
working with data cleaner and easier.
Merge branch 'newbuild'

The new build system is complete. This is the first step to spinning build.py
out of the arch zfs project and into its own project down the line once the
dust has settled.

The new build system relies on PKGBUILD.py which is imported into build.py.
Merge branch 'bugfix_repack_no_build_dir' into repo_support

These changes are to fix errors produced my makepkg when attempting to use the
repackage action on a _build_ tree that had previously not been built using the
build action.

The fix was to check for the '_build_/<group>/<package>/src' directory that is
produced by makepkg when building code. If this directory doesn't exist when
attempting to use the repackage action, the 'cd' command in the 'package()'
function of the package's PKGBUILD would cause makepkg to produce an error.
This in turn would cause the script to exit, potentially stopping work that
couldv'e proceded like building the source packages.

In the future, this script will be changed to use proper exceptions and log()
will not be allowed to exit the script in case of errors. This was only meant
to be a quick hack, but it is now being abused.
Merge branch 'bugfix_sources_order' into repo_support

Fixes "-s" action being completed before the "-b" or "-r" actions.
Start tracking archzfs repository
Reset hard coded linux version

When distributing pre-built packages for ZFS, it becomes necessary to have a
hard-coded kernel version. ZFS stores its module source headers in
"usr/src/spl-0.6.0-rc11/3.5.6-1-ARCH/", this causes the ZFS installation to
break on even minor point releases.

Due to the constant kernel upgrades in arch linux, this will be a pain.
Installing the standard ZFS packages from the repository will mean that the
user can not upgrade their kernel until the ZFS packages are updated in my
repository. This could possibly take some time depending on how fast upstream
moves to release fixes, and also how quickly I can push out updates.

One solution to this problem would be to release a DKMS version of the ZFS
packages which will recompile the ZFS and SPL kernel modules on every kernel
point release. I am working on these packages at the moment and they will be
released sometime in the future.
Update to zfs-0.6.0-rc12
Merge branch '0.6.0-rc12' into develop

Support for zfs-0.6.0-rc12.
Merge branch 'develop'

A big update with almost 100 commits!

* Support for zfs-0.6.0-rc12.
* Targets kernel 3.6.6.
* Support for creating signed repositories and packages.
* Bugfixes and documentation changes.
Initial commit
Merge branch 'move_wine_to_opt'
Update to 0.6.0-rc12-linux-3.6.7
Start tracking sources in REPO_PATH
Start tracking archnetflix repository
Update wine-silverlight to wine-1.5.18
Stop tracking index.html
Fix missing kernel modules

I stupidly repackage instead of building from scratch when packaging the
previous packages. From now on I will always build from scratch when packaging
new packages for distribution.

Other changes include:

* Fixed whitespace in the install files
* Increased pkgrel to 3
Fix broken pkgdesc in wine-silverlight

I filed a bug report for pkgdelta producing an error and discovered that the
pkgdesc variable had a newline in it that broke pkgdelta. I increased the
pkgrel to fix the messed up pkgdesc.
Update archzfs repo to pkgrel 4

This includes systemd unit file support and mkinitcpio hook updates.