Skip to contentSkip to conversation

trivial(?) question about post-installation scripts

DISCUSSION [email protected] 2 participants 4 messages Apr 4, 2020

lore
Share & tools
lore
#0 lore 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

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                         http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#1 lore raw
Quoted 12 lines · On Sat, 2020-04-04 at 05:52 -0400, [email protected] wrote:

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."

Quoted 6 lines

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.

I think however wrote it misunderstood. prerm and postrm are unlikely to run at image install time (but can if packages are removed). preinst will run.

Cheers,

Richard

#2 lore raw
Quoted 17 lines · Richard Purdie
Quoted 16 lines · On Sat, 2020-04-04 at 05:52 -0400, [email protected] wrote:

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?

Quoted 6 lines
Quoted 2 lines

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

I think however wrote it misunderstood. prerm and postrm are unlikely to run at image install time (but can if packages are removed). preinst will run.

i assumed as much (that preinst is perfectly capable of running at
image creation time). i may rewrite that section once i actually understand it in its entirety -- it's definitely a bit confusing at the moment.

rday

#3 lore raw
In reply to Richard Purdie
Quoted 17 lines · Richard Purdie
Quoted 16 lines · On Sat, 2020-04-04 at 05:52 -0400, [email protected] wrote:

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?

Quoted 6 lines
Quoted 2 lines

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

I think however wrote it misunderstood. prerm and postrm are unlikely to run at image install time (but can if packages are removed). preinst will run.

just to clarify a couple more points about those scripts (and i'm
definitely going to rewrite the dev manual section on this after i figure it out, with copious examples), as i read it, the pkg_postinst script will normally be run at one of two times:

* at image creation time if package is listed as part of the image, or
* at a later time on a running system

the difference being that the first case requires the process to recognize that the script is being run in the context of the image directory $D.

in some cases, it appears the script doesn't need to *explicitly*
check which context it's in, as using "$D" will automatically do the right thing. here's an example from shutdown-desktop.bb:

  pkg_postinst_${PN} () {
    grep -q qemuarm $D${sysconfdir}/hostname && \
        sed -i $D${datadir}/applications/shutdown.desktop -e
              's#^Exec=\(.*\)/halt#Exec=\1/reboot#' \
        || true
  }

so (and correct me if i'm wrong), the use of "$D" above will simply do the right thing as, in the first case, it will have the correct value (that is, ${D}), and in the latter case, it will be empty and so will simply work on a running system as well.

in other cases, however, depending on the context, there might need
to be tweaks, as in this case from modutils-initscripts.bb:

  pkg_postinst_${PN} () {
    if ${@bb.utils.contains('DISTRO_FEATURES','systemd','true','false',d)}; then
        if [ -n "$D" ]; then
            OPTS="--root=$D"     <-- trivial tweak for image build time
        fi
        systemctl $OPTS mask modutils.service
    fi
  }

in short, all pkg_postinst_* scripts need to access $D, at least implicitly, if they're designed to work in either context.

as for an example of pkg_postinst_ontarget(), i've already found
opkg-keyrings_1.0.bb, which most readers will understand should be run *only* at first boot time:

  pkg_postinst_ontarget_${PN} () {
  opkg-key populate
  }

slowly getting a handle on this ...

rday