From: Saul Wold <sgw@linux.intel.com>
To: Constantin Musca <constantinx.musca@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gnome-keyring: include unpackaged files with PAM enabled
Date: Thu, 27 Sep 2012 09:35:20 -0700 [thread overview]
Message-ID: <50648048.5040607@linux.intel.com> (raw)
In-Reply-To: <1348733857-18055-1-git-send-email-constantinx.musca@intel.com>
On 09/27/2012 01:17 AM, Constantin Musca wrote:
> Include missing files/dirs:
> ${base_libdir}/security/*.la
> ${base_libdir}/security/*${SOLIBSDEV}
> ${base_libdir}/security/.debug/
>
> [YOCTO #2805]
>
> Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
> ---
> meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb b/meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb
> index d822721..92e0e1b 100644
> --- a/meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb
> +++ b/meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb
> @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
>
> SECTION = "x11/gnome"
>
> -PR = "r9"
> +PR = "r10"
>
> inherit autotools gnome gtk-doc pkgconfig
>
> @@ -43,7 +43,10 @@ FILES_${PN} += "${datadir}/dbus-1/services ${datadir}/gcr"
>
> FILES_${PN}-dev += "${libdir}/${BPN}/devel/*.la \
> ${libdir}/${BPN}/devel/*${SOLIBSDEV} \
> - ${libdir}/${BPN}/standalone/*.la"
> + ${libdir}/${BPN}/standalone/*.la \
> + ${base_libdir}/security/*.la \
> + ${base_libdir}/security/*${SOLIBSDEV}"
>
> FILES_${PN}-dbg += "${libdir}/${BPN}/standalone/.debug/ \
> - ${libdir}/${BPN}/devel/.debug/"
> + ${libdir}/${BPN}/devel/.debug/ \
> + ${base_libdir}/security/.debug/"
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-09-27 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 8:17 [PATCH] gnome-keyring: include unpackaged files with PAM enabled Constantin Musca
2012-09-27 16:35 ` Saul Wold [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=50648048.5040607@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=constantinx.musca@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 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.