From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: "run-postinsts" added twice to PACKAGE_INSTALL
Date: Sun, 23 Oct 2016 08:51:25 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1610230847370.32524@localhost.localdomain> (raw)
minor observation ... messing with toolchains, and i noticed (via
"bb"):
$ bb show -r core-image-minimal PACKAGE_INSTALL
Parsing recipes..done.
# PACKAGE_INSTALL=${IMAGE_INSTALL} ${ROOTFS_BOOTSTRAP_INSTALL}
${FEATURE_INSTALL}
export PACKAGE_INSTALL="packagegroup-core-boot run-postinsts
run-postinsts "
wait a minute ... why is "run-postinsts" listed twice? (no harm, of
course, just superfluous.)
so ...
$ bb show -r core-image-minimal IMAGE_INSTALL
Parsing recipes..done.
# IMAGE_INSTALL=packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP}
${CORE_IMAGE_EXTRA_INSTALL}
IMAGE_INSTALL="packagegroup-core-boot run-postinsts "
$ bb show -r core-image-minimal ROOTFS_BOOTSTRAP_INSTALL
Parsing recipes..done.
# ROOTFS_BOOTSTRAP_INSTALL=${@bb.utils.contains("IMAGE_FEATURES",
"package-management", "", "${ROOTFS_PKGMANAGE_BOOTSTRAP}",d)}
ROOTFS_BOOTSTRAP_INSTALL="run-postinsts"
so it's being added both as part of IMAGE_INSTALL and as part of
ROOTFS_BOOTSTRAP_INSTALL. someone else is free to decide whether
that's worth caring about.
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:[~2016-10-23 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 12:51 Robert P. J. Day [this message]
2016-10-23 16:12 ` "run-postinsts" added twice to PACKAGE_INSTALL Khem Raj
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.20.1610230847370.32524@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