- fixed call of method textContent() on an undefined value
- added additional meta data file with suffix .pids. The file
  contains the information about the ID/Name of the root,boot
  readonly/readwrite device according to this appliance if a
  virtual disk based image was requested. The information is
  included as config.partids into the initrd and is used on
  first boot. Rather than guessing the purpose of partitions
  the initrd will now know it exactly
- switched vmxboot boot code to make use of config.partids
- switched oemboot boot code to make use of config.partids
- check for kiwi_BootPart from new partition IDs meta data
  in setupBootPartition(). This could be used to map the
  boot partition to another than the first partition
- fixed post partition size check and read-write dump if
  split + lvm is used. An undefined device was used for
  the check and the dump in this case
- make sure setupBootFlags also updates the .splash.gz variant of
  the initrd if the function was called with the non splash (.gz)
  variant of the initrd.
- fix typo and logic error in test cases (bnc #790254)
  * typo cause list comparison to fail
  * logic error caused a name that should have been in he comparison
    list to be omitted
- allow getExecArgsFormat to parse python optparse/argparse
  output. python uses the form '-o, --option' whereas we
  don't expect a comma between the short and long version
- add unit test for this option format
- use new partids hash to create the device map and cleanup
  access to the new device map data
- fixed use of filehandle in addAppdata() and collectPackages()
  of the instsource media KIWICollect module
- use new partids hash for the setup and installation of the
  bootloaders, setupBootLoaderConfiguration() / installBootLoader()
- use new partids hash for the bootloader stage setup
  setupBootLoaderStages()
- adapt oemboot suse/rhel-repart code to make use of the flexible
  boot partition location in $kiwi_BootPart. The partition ID
  stored there is used as the beginning of the partition layout.
  Instead of a fixed boot partition at 1 the layout handles the
  value of $kiwi_BootPart as the start. If there is no boot
  partition the first partition must be the root partition as
  usual.
- update the driver handling for the imageConfig data structure
  * take advantage of the private helper methods implemented for
    package handling
  * eliminates code duplication
  * simplifies implementation of driver handling methods
- update the unit tests to adjust for minor differences in messages
- resolve suse version checking to zero if the suse_version
  macro is not defined. This allows the package build going
  easily also in non-suse based distros
- fixed typo in setupFilesystem() which caused a fat16 filesystem
  even though a fat32 filesystem was requested.
- changed the efi boot partition type to fat16
- added ext2 modules to the bootx64.efi module
- added parted to openSUSE 12.2 JeOS template
- added support for a jump partition which is added before the
  actual boot partition. This is used for grub2 efi based disk
  images now. kiwi just put the created grub2 bootx64.efi module
  onto the fat16 based jump partition and let grub2 read all
  data from the second ext3 based boot partition. This allows
  standard linux filesystem based boot partitions and it has
  also turned out that this disk layout might be required for
  arm based images as well. But so far this system is connected
  to the efi setup only
- fixed logical volume name building in resizeLVMVolumes()
  the function only evaluates volume names at the primary
  level e.g /opt. As soon as you have a volume e.g /opt/bob
  it failed to resize