From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] subversion: inherit pkgconfig, so that serf can be found
Date: Tue, 29 Aug 2017 13:49:55 +0100 [thread overview]
Message-ID: <1504010995.2175.2.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170829114526.37559-2-alexander.kanavin@linux.intel.com>
On Tue, 2017-08-29 at 14:45 +0300, Alexander Kanavin wrote:
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> ---
> meta/recipes-devtools/subversion/subversion_1.9.6.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/subversion/subversion_1.9.6.bb
> b/meta/recipes-devtools/subversion/subversion_1.9.6.bb
> index b27115b981f..f49e26a5c8c 100644
> --- a/meta/recipes-devtools/subversion/subversion_1.9.6.bb
> +++ b/meta/recipes-devtools/subversion/subversion_1.9.6.bb
> @@ -8,7 +8,7 @@ HOMEPAGE = "http://subversion.tigris.org"
>
> BBCLASSEXTEND = "native"
>
> -inherit gettext
> +inherit gettext pkgconfig
>
> SRC_URI = "${APACHE_MIRROR}/${BPN}/${BPN}-${PV}.tar.bz2 \
> file://disable_macos.patch \
Any idea why we haven't had errors from this? Did it mean we just lost
something like https support?
Cheers,
Richard
next prev parent reply other threads:[~2017-08-29 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 11:45 [PATCH 1/3] pciutils: inherit pkgconfig so that libkmod can be found Alexander Kanavin
2017-08-29 11:45 ` [PATCH 2/3] subversion: inherit pkgconfig, so that serf " Alexander Kanavin
2017-08-29 12:49 ` Richard Purdie [this message]
2017-08-29 12:57 ` Alexander Kanavin
2017-08-29 14:11 ` Martin Jansa
2017-08-29 11:45 ` [PATCH 3/3] signing-keys: do not use DISTRO_VERSION in key names Alexander Kanavin
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=1504010995.2175.2.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox