From: Kang Kai <Kai.Kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] initscripts: add /sbin/sushell for systemd service debug-shell
Date: Tue, 7 Jul 2015 17:49:26 +0800 [thread overview]
Message-ID: <559BA0A6.20400@windriver.com> (raw)
In-Reply-To: <51025622cf3d8ae07bbf858b4ea9f55cda576fea.1436172370.git.kai.kang@windriver.com>
On 2015年07月06日 16:47, Kai Kang wrote:
> Add file /sbin/sushell for systemd service debug-shell which starts with
> /bin/sushell when SELinux is enabled. Copy and add sushell file from
> Fedora 22.
>
> Add runtime dependency bash as well when systemd is enabled to eliminate
> QA warning:
>
> WARNING: QA Issue: /sbin/sushell_initscripts contained in package initscripts
> requires /bin/bash, but no providers found in its RDEPENDS [file-rdeps]
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
> meta/recipes-core/initscripts/initscripts-1.0/sushell | 5 +++++
> meta/recipes-core/initscripts/initscripts_1.0.bb | 10 +++++++++-
> 2 files changed, 14 insertions(+), 1 deletion(-)
> create mode 100644 meta/recipes-core/initscripts/initscripts-1.0/sushell
>
> diff --git a/meta/recipes-core/initscripts/initscripts-1.0/sushell b/meta/recipes-core/initscripts/initscripts-1.0/sushell
> new file mode 100644
> index 0000000..7d96941
> --- /dev/null
> +++ b/meta/recipes-core/initscripts/initscripts-1.0/sushell
> @@ -0,0 +1,5 @@
> +#!/bin/bash
> +
> +[ -z "$SUSHELL" ] && SUSHELL=/bin/bash
> +
> +exec $SUSHELL
> diff --git a/meta/recipes-core/initscripts/initscripts_1.0.bb b/meta/recipes-core/initscripts/initscripts_1.0.bb
> index a086591..c2e815f 100644
> --- a/meta/recipes-core/initscripts/initscripts_1.0.bb
> +++ b/meta/recipes-core/initscripts/initscripts_1.0.bb
> @@ -33,6 +33,7 @@ SRC_URI = "file://functions \
> file://GPLv2.patch \
> file://dmesg.sh \
> file://logrotate-dmesg.conf \
> + ${@bb.utils.contains('DISTRO_FEATURES','systemd','file://sushell','',d)} \
It should check distro feature selinux rather than systemd that only
when selinux is enabled, debug-shell.service from systemd starts with
sushell.
I'll send V2.
Thanks,
Kai
> "
>
> S = "${WORKDIR}"
> @@ -46,7 +47,9 @@ DEPENDS_append = " update-rc.d-native"
> DEPENDS_append = " ${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd-systemctl-native','',d)}"
>
> PACKAGES =+ "${PN}-functions"
> -RDEPENDS_${PN} = "${PN}-functions"
> +RDEPENDS_${PN} = "${PN}-functions \
> + ${@bb.utils.contains('DISTRO_FEATURES','systemd','bash','',d)} \
> + "
> FILES_${PN}-functions = "${sysconfdir}/init.d/functions*"
>
> ALTERNATIVE_PRIORITY_${PN}-functions = "90"
> @@ -104,6 +107,11 @@ do_install () {
> if [ "${TARGET_ARCH}" = "arm" ]; then
> install -m 0755 ${WORKDIR}/alignment.sh ${D}${sysconfdir}/init.d
> fi
> +
> + if ${@bb.utils.contains('DISTRO_FEATURES','systemd','true','false',d)}; then
> + install -d ${D}/${base_sbindir}
> + install -m 0755 ${WORKDIR}/sushell ${D}/${base_sbindir}
> + fi
> #
> # Install device dependent scripts
> #
--
Regards,
Neil | Kai Kang
prev parent reply other threads:[~2015-07-07 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 8:47 [PATCH 0/1] Add /sbin/sushell when SELinux is enabled Kai Kang
2015-07-06 8:47 ` [PATCH 1/1] initscripts: add /sbin/sushell for systemd service debug-shell Kai Kang
2015-07-07 9:49 ` Kang Kai [this message]
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=559BA0A6.20400@windriver.com \
--to=kai.kang@windriver.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