* larchin - only basic features exist, with no documentation.


Changes 7.1 - 7.2

* Completely reworked the command-line interface (and consequently all
  the other code, too). Threading replaced to a large extent by separate
  processes. The GUI is now just a front end to the command-line tools.

*! Changed handling of pacman.conf. Now there is pacman.conf.repos
  instead of pacman.conf.larch, I hope it will be a bit easier to
  understand what happens when using a special version for installation.

* 'include' facility in package files: '+' + relative or absolute path

* Required/suggested packages included by default (data/requiredpacks) -
  they can be excluded by putting them in the veto file. The whole
  file can be overridden in addedpacks by starting it with '!!!'.

* Include directive ('+' + absolute or relative path to file) in
  package files.

* Boot loader configs for GRUB and syslinux included in the image, plus
  bootlines file, to ease transfer of built image to alternative medium.
  vesamenu.c32 is no longer supplied with larch, it is fetched from the
  Arch installation (syslinux).

* A command line option to live_part.py is available to override the
  profile's 'nosave' file, but this is always copied to the medium
  ('larch/nosave') - if it is present - to indicate the profile's
  'intention'.

* A file 'nosshkeys' in the profile suppresses generation of the host
  sshkeys (if openssh is installed - if not they wouldn't have been
  generated anyway). Previously this was only selectable as a direct
  build option (not stored anywhere).

* The root password can be supplied in the profile, in the file 'rootpw'.
  Previously this was not easily settable.

* Changed some options to mkisofs, generally to make it more similar to
  the partition builder (no -publisher, use -V instead of -A so
  that the name gets shown in file managers, -R instead of -r).

* When building an isolinux image, the 'isohybrid' script is called, so
  that the resulting 'iso' can be 'dd'ed to a USB-stick (see the isolinux
  documentation). This does not make the USB-stick session-save capable
  as the file-system it creates is not suitable, but it might be a
  useful distribution feature.

* Added ability to save and reuse generated locales, in a way similar
  to the saving of system.sqf.