From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>,
"Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: yocto@yoctoproject.org
Subject: Re: FW: stupid question about post-installation scripts
Date: Mon, 25 Nov 2013 17:06:51 +0000 [thread overview]
Message-ID: <197917002.9dER9YZC1c@helios> (raw)
In-Reply-To: <2877100.Goa8NZvDMD@helios>
On Monday 25 November 2013 17:01:10 Paul Eggleton wrote:
> On Monday 25 November 2013 15:21:41 Rifenbark, Scott M wrote:
> > >From: Robert P. J. Day [mailto:rpjday@crashcourse.ca]
> > >Sent: Sunday, November 24, 2013 2:37 AM
> > >To: Rifenbark, Scott M
> > >Subject: stupid question about post-installation scripts
> > >
> > > when one defines pkg_postinst scripts, are those scripts invoked at
> > >
> > >*both* root filesystem creation time and first boot time? so that one
> > >needs
> > >to manually check the value of ${D} to decide whether to run them, say,
> > >at
> > >first boot time?
>
> Not both - it's either-or; i.e. it will be run at rootfs creation time and
> if it fails then, it will be run on first boot. Yes you can use the value
> of $D (note: *not* ${D}!) to find out where the script is being called
> from, if necessary.
PS, if you really do want to force the script to be postponed until first boot,
you *must* make the postinst script fail if $D has a value - if you just let
it pass the system will assume it doesn't need to be called again on first
boot.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-11-25 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1311240533220.32547@oneiric>
2013-11-25 15:21 ` FW: stupid question about post-installation scripts Rifenbark, Scott M
2013-11-25 15:56 ` Bryan Evenson
2013-11-25 17:29 ` Robert P. J. Day
2013-11-25 17:41 ` Bryan Evenson
2013-11-25 17:01 ` FW: " Paul Eggleton
2013-11-25 17:06 ` Paul Eggleton [this message]
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=197917002.9dER9YZC1c@helios \
--to=paul.eggleton@linux.intel.com \
--cc=rpjday@crashcourse.ca \
--cc=scott.m.rifenbark@intel.com \
--cc=yocto@yoctoproject.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.