Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: can pkg_{pre, post}rm functions be run at all for image creation?
Date: Sun, 3 Aug 2014 02:56:04 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1408030254520.10897@localhost> (raw)
In-Reply-To: <20140802200959.GA22882@haswell>

On Sat, 2 Aug 2014, Khem Raj wrote:

> On 14-08-02 15:57:00, Robert P. J. Day wrote:
> > On Sat, 2 Aug 2014, Khem Raj wrote:
> >
> > > On Sat, Aug 2, 2014 at 9:34 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> > > > say, pkg_prerm() functions would never be written with respect to the
> > > > variable ${D}, which would be relevant only during image creation. but
> > > > i can see things like this in sysklogd.inc:
> > > >
> > > > pkg_prerm_${PN} () {
> > > >         if test "x$D" = "x"; then
> > >
> > > note that its not ${D} (bitbake context) but $D which is evaluated
> > > in the context when the script is run.
> >
> >   i still don't understand ... what are the possible values of $D
> > here, and what would they represent?
>
> At build time it will not be expanded by bitbake like ${D} is. but
> during image creation it will be. But when doing on-device install
> of this package $D will be empty. Its a way to differentiate actions
> during image creation and on-device install/update/remove

  but the yocto dev manual states pretty clearly that pkg_prerm and
pkg_postrm functions are *not* used during image creation. so you're
saying they are? under what circumstances?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



  reply	other threads:[~2014-08-03  6:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02 16:34 can pkg_{pre, post}rm functions be run at all for image creation? Robert P. J. Day
2014-08-02 19:40 ` Khem Raj
2014-08-02 19:57   ` Robert P. J. Day
2014-08-02 20:09     ` Khem Raj
2014-08-03  6:56       ` Robert P. J. Day [this message]
2014-08-04 12:37         ` Paul Eggleton
2014-08-04 13:42           ` Robert P. J. Day
2014-08-04 13:51             ` Paul Eggleton
2014-08-04 13:53             ` Richard Purdie
2014-08-04 13:56               ` Robert P. J. Day

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=alpine.LFD.2.11.1408030254520.10897@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox