From: ChenQi <Qi.Chen@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 6/7] curl: upgrade to 7.46
Date: Tue, 12 Jan 2016 09:18:20 +0800 [thread overview]
Message-ID: <5694545C.1050802@windriver.com> (raw)
In-Reply-To: <79D0CE6B-7A5E-4D08-BA90-06C6155E25D0@gmail.com>
On 01/12/2016 02:20 AM, Khem Raj wrote:
>> On Jan 10, 2016, at 9:58 PM, Chen Qi <Qi.Chen@windriver.com> wrote:
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>> meta/recipes-support/curl/{curl_7.45.0.bb => curl_7.46.0.bb} | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>> rename meta/recipes-support/curl/{curl_7.45.0.bb => curl_7.46.0.bb} (92%)
>>
>> diff --git a/meta/recipes-support/curl/curl_7.45.0.bb b/meta/recipes-support/curl/curl_7.46.0.bb
>> similarity index 92%
>> rename from meta/recipes-support/curl/curl_7.45.0.bb
>> rename to meta/recipes-support/curl/curl_7.46.0.bb
>> index a7ed778..8b109ba 100644
>> --- a/meta/recipes-support/curl/curl_7.45.0.bb
>> +++ b/meta/recipes-support/curl/curl_7.46.0.bb
>> @@ -14,8 +14,8 @@ SRC_URI = "http://curl.haxx.se/download/curl-${PV}.tar.bz2 \
>> #
>> SRC_URI += " file://configure_ac.patch"
>>
>> -SRC_URI[md5sum] = "62c1a352b28558f25ba6209214beadc8"
>> -SRC_URI[sha256sum] = "65154e66b9f8a442b57c436904639507b4ac37ec13d6f8a48248f1b4012b98ea"
>> +SRC_URI[md5sum] = "9979f989a2a9930d10f1b3deeabc2148"
>> +SRC_URI[sha256sum] = "b7d726cdd8ed4b6db0fa1b474a3c59ebbbe4dcd4c61ac5e7ade0e0270d3195ad"
>>
>> inherit autotools pkgconfig binconfig multilib_header
>>
>> @@ -55,4 +55,6 @@ PACKAGES =+ "lib${BPN}"
>> FILES_lib${BPN} = "${libdir}/lib*.so.*"
>> RRECOMMENDS_lib${BPN} += "ca-certificates"
>>
>> +FILES_${PN}-dev += "${datadir}/zsh”
> what files are in ${datadir}/zsh ?
Hi Khem,
There's only one file in this directory. See below.
chenqi@pek-hostel-deb01:~/poky/build-systemd [1] $ cat
tmp/work/armv5e-poky-linux-gnueabi/curl/7.46.0-r0/packages-split/curl-dev/usr/share/zsh/site-functions/_curl
#compdef curl
# curl zsh completion
local curcontext="$curcontext" state state_descr line
typeset -A opt_args
local rc=1
_arguments -C -S \
'*:URL:_urls' && rc=0
return rc
Best Regards,
Chen Qi
>> +
>> BBCLASSEXTEND = "native nativesdk"
>> --
>> 1.9.1
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2016-01-12 1:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 5:58 [PATCH 0/7] Package Upgrades Chen Qi
2016-01-11 5:58 ` [PATCH 1/7] pciutils: upgrade to 3.4.1 Chen Qi
2016-01-11 5:58 ` [PATCH 2/7] resolvconf: upgrade to 1.78 Chen Qi
2016-01-11 5:58 ` [PATCH 3/7] kmod: upgrade to 22 Chen Qi
2016-01-11 5:58 ` [PATCH 4/7] at: upgrade to 3.18 Chen Qi
2016-01-11 5:58 ` [PATCH 5/7] sysstat: upgrade to 11.2.0 Chen Qi
2016-01-11 5:58 ` [PATCH 6/7] curl: upgrade to 7.46 Chen Qi
2016-01-11 18:20 ` Khem Raj
2016-01-12 1:18 ` ChenQi [this message]
2016-01-12 1:23 ` Khem Raj
2016-01-12 2:03 ` ChenQi
2016-01-11 5:58 ` [PATCH 7/7] xz: upgrade to 5.2.2 Chen Qi
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=5694545C.1050802@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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