[oe] [RFC] make building working zaurus images easier

[Richard Purdie]

On Thu, 2007-07-26 at 14:11 +0200, Koen Kooi wrote:
>  For Spitz:
> 
>  #!/bin/sh
>  cd ${DEPLOY_DIR_IMAGE}
>  mkdir ${IMAGE_NAME}-installkit/
>  cp `ls zImage-2* | sort -b | uniq |tail -n1` ${IMAGE_NAME}-installkit/zImage.bin
>  cp `ls ${IMAGE_NAME}.rootfs*gz | sort -b | uniq |tail -n1`
>  ${IMAGE_NAME}-installkit/hdimage1.tgz
>  cp updater.sh.${MACHINE} ${IMAGE_NAME}-installkit/updater.sh
>  cp gnu-tar ${IMAGE_NAME}-installkit/
>  tar czf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit.tar.gz
> ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit/
> 
> > Comments/improvements/flames?

Why not just write one decent script instead of 3+ forks?

if [ "${MACHINE}" = "spitz" ]; then
    cp gnu-tar ${IMAGE_NAME}-installkit/
fi

etc.

This is probably suitable material for a do_deploy image.bbclass task.
The guts of the task can live in the machine specific files (such as the
zaurus common file) as a function added into the task by some new
variable. Does that seem reasonable?

Richard