public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "rpjday@crashcourse.ca" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: trivial(?) question about post-installation scripts
Date: Sat, 4 Apr 2020 05:52:46 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.2004040549380.6252@localhost.localdomain> (raw)


  still working my way through the YP docs and, in dev manual, 3.3.19,
"Post-Installation Scripts", one reads the final note:

"Equivalent support for pre-install, pre-uninstall, and post-uninstall
scripts exist by way of pkg_preinst, pkg_prerm, and pkg_postrm,
respectively. These scrips work in exactly the same way as does
pkg_postinst with the exception that they run at different times.
Also, because of when they run, they are not applicable to being run
at image creation time like pkg_postinst."

  i'm confused ... why would a pkg_preinst script not be applicable to
being run at image creation time? or am i misreading that?

  i'll probably have more questions about these scripts as i dig
further into them.

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:[~2020-04-04  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04  9:52 rpjday [this message]
2020-04-04  9:58 ` [OE-core] trivial(?) question about post-installation scripts Richard Purdie
2020-04-04 10:14   ` rpjday
2020-04-04 11:03   ` rpjday

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.21.2004040549380.6252@localhost.localdomain \
    --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