From: Rongqing Li <rongqing.li@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 1/1] quagga: add pam support for vtysh
Date: Fri, 8 Nov 2013 13:08:15 +0800 [thread overview]
Message-ID: <527C71BF.3020002@windriver.com> (raw)
In-Reply-To: <568c0cba0af47d5f6a0402ef4ac8316db7769326.1383884700.git.hongxu.jia@windriver.com>
On 11/08/2013 12:32 PM, Hongxu Jia wrote:
> According to DISTRO_FEATURES to add pam support for quagga, and import
> configure file from Fedora.
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
> meta-networking/recipes-protocols/quagga/files/quagga.pam | 13 +++++++++++++
> meta-networking/recipes-protocols/quagga/quagga.inc | 13 ++++++++++++-
> 2 files changed, 25 insertions(+), 1 deletion(-)
> create mode 100644 meta-networking/recipes-protocols/quagga/files/quagga.pam
>
> diff --git a/meta-networking/recipes-protocols/quagga/files/quagga.pam b/meta-networking/recipes-protocols/quagga/files/quagga.pam
> new file mode 100644
> index 0000000..3541a97
> --- /dev/null
> +++ b/meta-networking/recipes-protocols/quagga/files/quagga.pam
> @@ -0,0 +1,13 @@
> +#
> +# The PAM configuration file for the quagga `vtysh' service
> +#
> +
> +# This allows root to change user infomation without being
> +# prompted for a password
> +auth sufficient pam_rootok.so
> +
> +# The standard Unix authentication modules, used with
> +# NIS (man nsswitch) as well as normal /etc/passwd and
> +# /etc/shadow entries.
> +auth include common-auth
> +
> diff --git a/meta-networking/recipes-protocols/quagga/quagga.inc b/meta-networking/recipes-protocols/quagga/quagga.inc
> index 2106c9b..52cd7a3 100644
> --- a/meta-networking/recipes-protocols/quagga/quagga.inc
> +++ b/meta-networking/recipes-protocols/quagga/quagga.inc
> @@ -32,10 +32,12 @@ SRC_URI = "http://download.savannah.gnu.org/releases/quagga${QUAGGASUBDIR}/quagg
> file://watchquagga.init \
> file://watchquagga.default \
> file://volatiles.03_quagga \
> + file://file://quagga.pam \
Why is there be two file://?
> file://ripd-fix-two-bugs-after-received-SIGHUP.patch"
>
> -PACKAGECONFIG ??= ""
> +PACKAGECONFIG ??= "${@base_contains('DISTRO_FEATURES', 'pam', 'pam', '', d)}"
> PACKAGECONFIG[cap] = "--enable-capabilities,--disable-capabilities,libcap"
> +PACKAGECONFIG[pam] = "--with-libpam, --without-libpam, libpam"
>
> inherit autotools update-rc.d useradd
>
> @@ -98,6 +100,15 @@ do_install () {
> # Remove generated info dir file, it doesn't belong in the generated
> # package.
> rm -f ${D}${infodir}/dir
> +
> + # For PAM
> + for feature in ${DISTRO_FEATURES}; do
> + if [ "$feature" = "pam" ]; then
> + install -D -m 644 ${WORKDIR}/quagga.pam ${D}/${sysconfdir}/pam.d/quagga
> + break
> + fi
> + done
> +
Could you use the below method to simply this loop
if
${@base_contains('DISTRO_FEATURES','sysvinit','false','true',d)};then
if
-Roy
> }
>
> # Split into a main package and separate per-protocol packages
>
--
Best Reagrds,
Roy | RongQing Li
next prev parent reply other threads:[~2013-11-08 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 4:32 [PATCH 0/1] quagga: add pam support for vtysh Hongxu Jia
2013-11-08 4:32 ` [PATCH 1/1] " Hongxu Jia
2013-11-08 5:08 ` Rongqing Li [this message]
2013-11-08 8:30 ` Hongxu Jia
2013-11-08 8:34 ` [PATCH 0/1] " Hongxu Jia
2013-11-26 16:23 ` Joe MacDonald
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=527C71BF.3020002@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-devel@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