From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/4] bash: package bashbug separately
Date: Thu, 9 Mar 2017 22:23:29 +0200 [thread overview]
Message-ID: <20170309202331.5595-2-alexander.kanavin@linux.intel.com> (raw)
In-Reply-To: <20170309202331.5595-1-alexander.kanavin@linux.intel.com>
It's a machine-specific script, which is causing conflicts
when multiple versions of bash are installed in multilib setting,
and it also does not really make sense for embedded systems anyway.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
meta/recipes-extended/bash/bash.inc | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-extended/bash/bash.inc b/meta/recipes-extended/bash/bash.inc
index a05b987b87b..3e9c6625693 100644
--- a/meta/recipes-extended/bash/bash.inc
+++ b/meta/recipes-extended/bash/bash.inc
@@ -65,3 +65,7 @@ pkg_postinst_${PN} () {
pkg_postrm_${PN} () {
printf "$(grep -v "^${base_bindir}/bash$" $D${sysconfdir}/shells)\n" > $D${sysconfdir}/shells
}
+
+PACKAGES += "${PN}-bashbug"
+FILES_${PN} = "${bindir}/bash ${base_bindir}/bash.bash"
+FILES_${PN}-bashbug = "${bindir}/bashbug"
--
2.11.0
next prev parent reply other threads:[~2017-03-09 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 20:23 [PATCH 1/4] glibc: do the multilib_header magic also for bits/long-double.h Alexander Kanavin
2017-03-09 20:23 ` Alexander Kanavin [this message]
2017-03-09 20:23 ` [PATCH 3/4] db: do the multilib_header processing for db.h Alexander Kanavin
2017-03-09 20:23 ` [PATCH 4/4] gpgme: fix python module build and installation Alexander Kanavin
2017-03-10 10:51 ` Burton, Ross
2017-03-10 11:03 ` Alexander Kanavin
2017-03-11 13:47 ` Richard Purdie
2017-03-11 16:05 ` Richard Purdie
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=20170309202331.5595-2-alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--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