All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Krelin <hacker@klever.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] make building working zaurus images easier
Date: Fri, 27 Jul 2007 10:47:06 +0200	[thread overview]
Message-ID: <46A9B10A.4020308@klever.net> (raw)
In-Reply-To: <46A9AC1C.1070508@dominion.kabel.utwente.nl>

>>> Michael Krelin schreef:
>>>> I have never looked into all this machinery, but since we have, e.g.
>>>> x11-image-spitz.tar.gz 
> 
> IMAGE_NAME = "${IMAGE_BASENAME}-${MACHINE}-${DATETIME}" :)
> 
>>>> and zImage-spitz.bin symlinks, I'd guess that we 
>>>> can do without these somewhat ugly when unnecessary `ls|sort|uniq|tail` 
>>>> things, can't we?
>>> Won't tar package up the symlinks instead of the real files in that case?
>> Yes, but we can use readlink to work out the real file...
> 
> How about this:
> 
> cd ${DEPLOY_DIR_IMAGE}
> mkdir ${IMAGE_NAME}-installkit/
> 
> # Get the latest kernel using the zImage-<machine>.bin symlink
> cp `readlink zImage-${MACHINE}.bin` ${IMAGE_NAME}-installkit/zImage.bin

hmm.. isn't that equivalent to

cp zImage-${MACHINE}.bin ${IMAGE_NAME}-installkit/zImage.bin

? cp surely will dereference symlink unless asked not to.

Love,
H

> 
> if [ "${MACHINE}" = "spitz" ]; then
>     cp gnu-tar ${IMAGE_NAME}-installkit/
>     cp ${IMAGE_NAME}.rootfs.tar.gz ${IMAGE_NAME}-installkit/hdimage1.tgz
> else
>     cp ${IMAGE_NAME}.rootfs.jffs2 ${IMAGE_NAME}-installkit/initrd.bin
> fi
> 
> # All zaurus machines except collie need updater.sh
> if [ "${MACHINE}" != "collie" ]; then
>     cp updater.sh.${MACHINE} ${IMAGE_NAME}-installkit/updater.sh
> fi
> 
> tar czf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit.tgz {IMAGE_NAME}-installkit/
> rm -rf ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}-installkit/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> 
> iD8DBQFGqawcMkyGM64RGpERAvEQAKC3czWwnPBjw6gvh06AcVj3aoU7pQCgvJpc
> hhLFEF/cZBgUB9TGMZMPkFk=
> =/QP0
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2007-07-27  8:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 11:48 [RFC] make building working zaurus images easier Koen Kooi
2007-07-26 11:57 ` Marcin Juszkiewicz
2007-07-26 12:11 ` Koen Kooi
2007-07-26 12:30   ` Richard Purdie
2007-07-26 12:44     ` Koen Kooi
2007-07-26 13:19 ` Michael Krelin
2007-07-26 16:51   ` Richard Purdie
2007-07-26 17:36   ` Koen Kooi
2007-07-26 18:04     ` Michael Krelin
2007-07-26 18:39     ` Richard Purdie
2007-07-27  8:26       ` Koen Kooi
2007-07-27  8:47         ` Michael Krelin [this message]
2007-07-27  9:54           ` Koen Kooi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46A9B10A.4020308@klever.net \
    --to=hacker@klever.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.