- added better comments describing what eltorito boot image
  is used for an install ISO
- on construction of a KIWIXML instance, return early if no
  pointer to the image configuration directory is defined
- Use isolinux to boot an install CD
  + Instead of using the bootloader selected for the image raw
    disk to boot the install iso we use isolinux which is the
    correct loader for an iso. In addition this now also allows
    to create hybrid install iso images
- Update all JeOS templates to include the gfxboot-branding if
  the selected image type is "oem". This is done to have a graphics
  boot menu for install iso images
- fixed dn() function to work correctly with loop devices (bnc #855288)
- fixed setupBootLoaderStages grub module setup (bnc #847912)
  * prevent the use of insmod and put them into the grub2 loader
    module directly. For secure boot dynamic loading of modules
    is not allowed and we also fix the undefined symbols problem
    as described in the bug
- arm: make sure there is no x86 boot code in MBR
- arm: make sure the fat32 filesystem is created with the -I option
  + See mkdosfs for details on the -I switch. This finally fixes
    the boot problems on the Raspberry-Pi boards
- make sure gfxterm and gfxmenu are embedded into grub loader module
- arm: berryboot fixes
  * berryboot can't read directories, thus we have to keep kernel
    and initrd and all other files on the toplevel of the fat32
  * berryboot does not pass ATAG_INITRD2 to the kernel, thus we
    have to set address and size ourselves
- Update copyBootCode function
  * Add support to check for /boot/dtb/ since DTB files
    will be stored in this folder
- Add templates for ppc64le
- v5.06.14 released
- KIWIAnalyeCustomData:
  Create a custom.json file in addition to the custom dir tree
  The custom.json file contains the name, directory, binary
  and permission information for each file we found and
  categorized as unmanaged
- fixed boot of split systems
  * the loop device setup for the read-only squashfs part was broken
- cleanup variable setup for oemboot
  * remove unused variable required for isoboot only
- Cleanup isoboot code
  * prevent use of fixed loop device name
- v5.06.15 released
Switch to kmod-compat

Otherwise you'll get a conflict in the build service:
conflict for provider of module-init-tools needed by
kiwi-desc-oemboot-requires, (provider module-init-tools is conflicted by
installed kmod-compat)
- move the filesystem options into an Object
  + eliminate a method in the Globals singleton that is FS independent,
    confusing and returns data structure that gets indexed, making data
    access error prone
  + first step to moving filesystem options into XML and unifying it
    with existing ZFS setting in the XML
  + we should not have disconnected ways of dealing with filesystem options
  + this will help with the implementation of *Builder classes for the
    various filesystems
- fix type in the command line test trigger
- fix inconsistency when applying tune options for ext file systems for the
  root file system
  + previously it was possible that both user specified tune options and
    built in kiwi option were passed to tune2fs. The tune2fs manpage does
    not specify the behavior when the same option is specified twice