live-helper 1.0.6 will be the last release of live-helper 1.x, which will
produce lenny 5.0.3 release images. However, when 5.0.4 is due, we'll need
to produce new images with slightly modified functions/release.sh files.
In order to acchieve that, we'll allow to have such a file overload the
functions shipped in live-helper.
This way, we can acchieve that:
* live-helper itself doesn't need to be updated through stable updates
anymore.
* we still can do the required changes for a new point release.
* we even ship the changes in the source tarballs automatically.
console-setup is not essential per se, but without it, the preseed
boot parameters for keyboard layouts do not work. Those are needed
when we're going to use gfxboot. And that on the other hand, will
be pretty much standard, therefore including an additional package
in the standard list seems ok.
* several rephrasing to clarify/correct things because some wording
was ambiguous/wrong.
* changed instructions to use a mounted partition when creating the
file. In the previous instructions the present directory was used and
if it was $HOME, then the file was created in the live memory
(aufs/unionfs). Of course using memory to create the file would limit
the size of the file to the size of free memory.
* moved part of the instructions to inside create-lukshome-file.sh so
the user can see them because the hook itself is not saved in the
built live system.
* added a check to see if /mnt directory is empty.
* added some missing "umounts" and "cryptsetup remove" in some error checks.
* removed the proposal of copying from another mounted /home/
directory. It could be confusing to the user. The user should do it
later, with the live system booted with lukshome boot option, which
should be the next thing he/she will do anyway.
* renamed variable ERROR_LEVEL to EXIT_CODE (sounded too much a
redmond batch file).
Adding the ability to disable use of the GTK graphical
debian-installer is handy either to reduce the size of the
images or if the necessary files aren't available.
If you attempt a build and it fails for whatever reasons (say, a
configuration issue) and then you retry your build without calling
lh_clean, you can sometimes run into an issue with the
'deconfiguring file /bin/hostname' step. It'll try to move
chroot/bin/hostname.orig to chroot/bin/hostname but
chroot/bin/hostname.orig won't exist as chroot/bin/hostname hasn't
been moved aside like it expects (ie. the original file is still
chroot/bin/hostname). This is frustrating since if the error was
ignored, the build would be able to complete successfully and as
expected. So, let lh_chroot_hostname check if
'chroot/bin/hostname.orig' exists before attempting to
move it to 'chroot/bin/hostname'.
First, we'll make it conditional on the existence of a replacement graphic.
Second, the location of the replacement graphic shall be in the config tree,
not on the binary image.
Daniel Baumann
Cody A.W. Somerville
Rui Miguel Bernardo