dummy start-stop-daemon after lh clean --binary (?)

[Tzafrir Cohen <tzafrir.cohen@xorcom.com>]

Hi

Back to my original issue:

My build script runs:



#!/bin/sh

set -e

# Basically a wrapper for lh_local . Also chdirs into build/
. tools/lh_run

LOG_FILE=$build_root/log

set_conf() {
  lh config --conffile ./config.cfg "$@"
}

chroot_done=false

build_type() {
  type="$1"
  exten=".$type"
  case "$type" in
    usb-hdd) exten=".img";;
    net) exten="-net.tar.gz";;
  esac

  set_conf --binary-images "$type"
  if $chroot_done
  then
    lh clean --binary
    lh binary
  else
    lh clean --all
    lh build
    chroot_done=true
  fi
  mv binary$exten tmp/
}

mkdir -p tmp/

main() {
  build_type iso

  build_type usb-hdd

  #build_type net
}

main 2>&1 | tee $LOG_FILE

mv tmp/* .




So basically I have something that should be the equivalent of:

./live-helper/helpers/local config -b iso
./live-helper/helpers/local clean --all
./live-helper/helpers/local build

./live-helper/helpers/local config -b hdd-usb
./live-helper/helpers/local clean --binary
./live-helper/helpers/local binary


The first binary image (the .iso) is generated OK. The second one,
however, is generated with the dummy "exit 0" shell script as
/sbin/start-stop-daemon (the one generated in chroot_dpkg).


At the moment I have a work-around ('lh clean --all' and 'lh build' for
both) and more pressing issues to fix.

But if anybody happens to find a bug there, or something that I did
wrong, I'd appreciate a ping.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen@xorcom.com
+972-50-7952406           mailto:tzafrir.cohen@xorcom.com
http://www.xorcom.com  iax:guest@local.xorcom.com/tzafrir