From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Colin Walters <walters@verbum.org>
Cc: poky <poky@yoctoproject.org>
Subject: Re: post-image-creation postinsts
Date: Tue, 03 May 2011 11:36:51 +0100 [thread overview]
Message-ID: <1304419011.21461.98.camel@rex> (raw)
In-Reply-To: <BANLkTimaSk6vz1AeoRoT63T24XX=w1TuaA@mail.gmail.com>
On Mon, 2011-05-02 at 11:12 -0400, Colin Walters wrote:
> Currently from poky-bernard-5.0, in gdk-pixbuf_2.22.1.bb, we have:
>
> postinst_pixbufloader () {
> if [ "x$D" != "x" ]; then
> exit 1
> fi
>
> GDK_PIXBUF_MODULEDIR=${libdir}/gdk-pixbuf-2.0/${LIBV}/loaders
> gdk-pixbuf-query-loaders --update-cache
>
> test -x ${bindir}/gtk-update-icon-cache && gtk-update-icon-cache -q
> ${datadir}/icons/hicolor
> }
>
> This results in a first-boot icon cache query in my image, which is
> pretty lame since we could equally well do this after the image is
> generated, and not on every computer that boots the image.
>
> It seems to me we could add some mechanism for mounting the image
> filesystem and running a script in there (guestfs?), or maybe an
> automated QEMU boot, run the postinsts, and sync/shutdown?
>
> Thoughts?
The lines at the top:
if [ "x$D" != "x" ]; then
exit 1
fi
force the script to run on the target device. If there is a way to run
this at image generation time (cross safe), tell us what it is and we
can make it happen at image generation time!
(postinstalls are run at image generation time with $D set to the
directory containing the image).
Cheers,
Richard
next prev parent reply other threads:[~2011-05-03 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 15:12 post-image-creation postinsts Colin Walters
2011-05-02 15:31 ` Mark Hatle
2011-05-03 10:36 ` Richard Purdie [this message]
2011-05-03 23:01 ` Colin Walters
2011-05-03 23:15 ` Richard Purdie
2011-05-03 23:22 ` Joshua Lock
2011-05-03 23:38 ` Mark Hatle
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=1304419011.21461.98.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=poky@yoctoproject.org \
--cc=walters@verbum.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.