From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Mark Asselstine <asselsm@gmail.com>,
<meta-virtualization@yoctoproject.org>
Subject: Re: [PATCH] libvirt: add PACKAGECONFIG for sasl
Date: Wed, 30 Oct 2013 23:59:58 -0400 [thread overview]
Message-ID: <5271D5BE.5010409@windriver.com> (raw)
In-Reply-To: <1383184512-28442-1-git-send-email-asselsm@gmail.com>
On 13-10-30 9:55 PM, Mark Asselstine wrote:
> We don't want to leave build order dictating whether or not we get
> sasl support in libvirt so add a PACKAGECONFIG for sasl. I have not
> added sasl as a default PACKAGECONFIG since out of the box you would
> not normally get sasl being built so this mimics this behavior. I have
> listed a RDEPENDS in the PACKAGECONFIG as older Yocto builds for some
> reason are not picking up the required runtime dependency.
This makes sense to me. I queued the patch, and if no one objects, I
can push it tomorrow.
Bruce
>
> Signed-off-by: Mark Asselstine <asselsm@gmail.com>
> ---
> recipes-extended/libvirt/libvirt_1.1.2.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/recipes-extended/libvirt/libvirt_1.1.2.bb b/recipes-extended/libvirt/libvirt_1.1.2.bb
> index 56d6aed..4bdade8 100644
> --- a/recipes-extended/libvirt/libvirt_1.1.2.bb
> +++ b/recipes-extended/libvirt/libvirt_1.1.2.bb
> @@ -149,6 +149,7 @@ PACKAGECONFIG[udev] = "--with-udev --with-pciaccess,--without-udev,udev libpciac
> PACKAGECONFIG[selinux] = "--with-selinux,--without-selinux,libselinux,"
> PACKAGECONFIG[ebtables] = "ac_cv_path_EBTABLES_PATH=/sbin/ebtables,ac_cv_path_EBTABLES_PATH=,ebtables,ebtables"
> PACKAGECONFIG[python] = "--with-python,--without-python,python,"
> +PACKAGECONFIG[sasl] = "--with-sasl,--without-sasl,cyrus-sasl,cyrus-sasl"
>
> # Enable the Python tool support
> require libvirt-python.inc
>
prev parent reply other threads:[~2013-10-31 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 1:55 [PATCH] libvirt: add PACKAGECONFIG for sasl Mark Asselstine
2013-10-31 3:59 ` Bruce Ashfield [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=5271D5BE.5010409@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=asselsm@gmail.com \
--cc=meta-virtualization@yoctoproject.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.