From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: can pkg_{pre, post}rm functions be run at all for image creation?
Date: Sat, 2 Aug 2014 12:34:50 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1408021229180.24061@localhost> (raw)
followup to earlier note, is it true that the pkg_prerm and
pkg_postrm functions cannot be run at all during image creation, but
only on the actual running target? this would seem reasonable as it
doesn't seem to make sense to be running any sort of removal code
during image creation.
(i'm assuming that it is never the case that any sort of package
removal is done during image creation, and that the creation process
will install *only* those packages that should be part of the final
image, is that correct?)
however, if the above is correct, then it would make sense that all,
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
if test "$1" = "upgrade" -o "$1" = "remove"; then
/etc/init.d/syslog stop
fi
fi
}
so what does that mean?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-08-02 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 16:34 Robert P. J. Day [this message]
2014-08-02 19:40 ` can pkg_{pre, post}rm functions be run at all for image creation? 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
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.1408021229180.24061@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox