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

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Purdie schreef:
> 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

I was thinking of that just now :)

> 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?

Very reasonable! Would this also be the time to discuss a kernel deploy task?

regards,

Koen


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGqJdJMkyGM64RGpERAgEOAKCWaIaePMGH4QVbjnDGy8s45Xdh0wCffQ3T
s3yx50FzrnKb/r98XL+JfiA=
=nZsH
-----END PGP SIGNATURE-----