From: Florin Sarbu <florin.sarbu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] systemd: Fix packaging of pam config files.
Date: Wed, 20 Nov 2013 12:52:01 +0200 [thread overview]
Message-ID: <528C9451.3030703@windriver.com> (raw)
In-Reply-To: <1384517411-27854-1-git-send-email-florin.sarbu@windriver.com>
Hi,
did anybody have the time to look over this?
Thanks.
On 11/15/2013 02:10 PM, Florin Sarbu wrote:
> Removed early FILES_${PN} += for the pam config
> files which would subesequently be overwritten by
> a FILES_${PN} = .
>
> Signed-off-by: Florin Sarbu <florin.sarbu@windriver.com>
> ---
> meta/recipes-core/systemd/systemd_208.bb | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/meta/recipes-core/systemd/systemd_208.bb b/meta/recipes-core/systemd/systemd_208.bb
> index 8c70fe5..66e6bee 100644
> --- a/meta/recipes-core/systemd/systemd_208.bb
> +++ b/meta/recipes-core/systemd/systemd_208.bb
> @@ -160,8 +160,6 @@ FILES_${PN}-kernel-install = "${bindir}/kernel-install \
> FILES_${PN}-rpm-macros = "${exec_prefix}/lib/rpm \
> "
>
> -FILES_${PN} += "${@base_contains('DISTRO_FEATURES', 'pam', '${sysconfdir}/pam.d', '', d)}"
> -
> FILES_${PN}-zsh = "${datadir}/zsh/site-functions"
>
> FILES_${PN}-binfmt = "${sysconfdir}/binfmt.d/ \
> @@ -213,6 +211,7 @@ FILES_${PN} = " ${base_bindir}/* \
> /lib/udev/rules.d/71-seat.rules \
> /lib/udev/rules.d/73-seat-late.rules \
> /lib/udev/rules.d/99-systemd.rules \
> + ${@base_contains('DISTRO_FEATURES', 'pam', '${sysconfdir}/pam.d', '', d)} \
> "
>
> FILES_${PN}-dbg += "${rootlibdir}/.debug ${systemd_unitdir}/.debug ${systemd_unitdir}/*/.debug ${base_libdir}/security/.debug/"
prev parent reply other threads:[~2013-11-20 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 12:10 [PATCH] systemd: Fix packaging of pam config files Florin Sarbu
2013-11-20 10:52 ` Florin Sarbu [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=528C9451.3030703@windriver.com \
--to=florin.sarbu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.