- improved/changed image caching system
  * switched from btrfs to overlayfs
  * no loop mounts involved anymore, thus one layer less
  * using native kernel overlay filesystem which performs
    better than fuse based filesystems. btrfs has turned out
    to work unstable when using loop devices and I could not
    find a noticeable performance difference between
    btrfs seed devices and the overlayfs upper/lower system
  * no cache files but cache trees. full freedom for the user
    to store those data on NFS, tmpfs, read-only locations...
  * all package solver tasks now done via satsolver, solvables
    will also be cached, no hacky ignore of packages in the
    cache selection code
  * following the keep it simple principle. the caching code
    is now pretty straight forward
- update default strip data to make the initrd a bit smaller
  * remove /usr/share/grub2/backgrounds
  * remove /usr/share/kbd
  * remove /usr/lib/rpm
- fixed suseGFXBoot to work correctly if a two bootloader
  setup is requested like it is the case with EFI capable
  hybrid iso's. They use isolinux/gfxboot for the bios boot
  case and grub2/grub2-branding for the EFI boot. Thus the
  branding data needs to be handled for both and not only
  one loader
- use xz compressor for live iso's based on overlayfs
- fixes for openSUSE 13.1 boot descriptions
  * removed support for legacy grub
  * add Mesa to delete list, for some reason that gets
    pulled in now so we make sure it will be removed
- v5.05.13 released
- Revert "- moved default kiwi cache image location" according
  to FHS /var/tmp/kiwicache is not allowed. This reverts
  commit: 5d667b7bb2d1774fe02835e378788638fcf9c582
- Revert "- DB: update documentation, changed cache location"
  This reverts commit: 5e8a4ba11f6a8b29e2a60df91bd16e0c27adca35
- DB: rebuild documentation
- v5.05.14 released
- fixed structure of unpacked image tree when build with a cache
  In order to avoid any conflicts concerning code operating on
  the unpacked image tree it's required that the structure with
  and without using a base cache image is the same
- v5.05.15 released
- fixed __populateDriverInfo
  * the function did not work correctly with the default profile
    name. It uses the kiwi internal default profile name 'kiwi_default'
    as real profile name and failed to use a section as default
    section if the 'default' profile name was explicitly specified
    like it is the case for the netboot boot image descriptions
- cleanup KIWIXML constructor
  * The object variables $this->{buildType} and $this->{defaultType}
    were used without any real context and are just a copy of
    $imageType and $this->{selectedType}
- fixed unaligned done flags
- adapt handling of bootkernel and bootprofile to new data structure
  * there is still the function __populateDefaultProfiles_legacy
    active and working but as soon as this code will go away the
    transfer of the 'bootkernel' and 'bootprofile' attributes from
    the system image into the boot image must follow the new data
    structure which is based on get and set methods. Actually this
    change also fixes the creation of the .profile kiwi_drivers
    data because the code writing this is already based on the new
    internal data structure and was missing the correct boot
    profile information according to bootkernel and bootprofile
- cleanup code, prevent warning messages
- restructure the use of prebuilt boot images
  * adapt to new data structure thus we get rid of
    checkAndSetupPrebuiltBootImage, getDefaultPrebuiltDir_legacy
  * moved the logic for using a prebuilt version of a boot image
    into the image creator code at the level of prepareBootImage
    and createBootImage. This saves us one KIWIXML instance
  * write one function createImageBootImage which does either
    the prepare/create of the boot image or the use of an existing
    prebuilt version. reduces some code duplication
- fixed __checkSystemDiskData runtime check to work correctly
  with the 'all' size specification
- fixed and optimized disk size calculation
  * I had by default 40% spare space on the root path which seems to
    be too much, I have 20% spare on each volume so I adapted that
    to the root path as well.
  * for the size estimation I now use the --apparent-size option in
    du, which works better on files with holes and other or other
    attributes which makes a difference when copying those data.
  * Use a fixed value for the filesystem overhead each volume adds
    to the disk. It is wrong to calculate and add a 20% spare/volume
    according to the size of the data in the volume to the disk,
    because that value has already been taken into account with
    the data spare calculation of the entire tree