From: Robert Yang <liezhi.yang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 2/2] bzip2: remove bzip2-dev from PACKAGES
Date: Wed, 8 Apr 2015 09:55:57 +0800 [thread overview]
Message-ID: <55248AAD.7010503@windriver.com> (raw)
In-Reply-To: <27D7EBDF-FA94-4B14-B185-69C3BD080239@gmail.com>
On 04/08/2015 09:34 AM, Khem Raj wrote:
>
>> On Apr 7, 2015, at 5:58 AM, Robert Yang <liezhi.yang@windriver.com> wrote:
>>
>> There should be only one dev package which is libbz2-dev, so remove
>> bzip2-dev.
>>
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>> meta/recipes-extended/bzip2/bzip2_1.0.6.bb | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-extended/bzip2/bzip2_1.0.6.bb b/meta/recipes-extended/bzip2/bzip2_1.0.6.bb
>> index ed12277..d1d1c8d 100644
>> --- a/meta/recipes-extended/bzip2/bzip2_1.0.6.bb
>> +++ b/meta/recipes-extended/bzip2/bzip2_1.0.6.bb
>> @@ -17,6 +17,7 @@ SRC_URI[md5sum] = "00b516f4704d4a7cb50a1d97e6e8e15b"
>> SRC_URI[sha256sum] = "a2848f34fcd5d6cf47def00461fcb528a0484d8edef8208d6d2e2909dc61d9cd"
>>
>> PACKAGES =+ "libbz2 libbz2-dev libbz2-staticdev"
>> +PACKAGES_remove = "bzip2-dev bzip2-staticdev”
>
> why remove ${PN}-dev ? others should be removed IMO
I think that it had added libbz2-dev was because debian/ubuntu uses
libbz2-dev, the similar to xz.
// Robert
>
>>
>> CFLAGS_append = " -fPIC -fpic -Winline -fno-strength-reduce -D_FILE_OFFSET_BITS=64"
>>
>> @@ -35,7 +36,7 @@ do_install_ptest () {
>>
>> FILES_libbz2 = "${libdir}/lib*${SOLIBS}"
>>
>> -FILES_libbz2-dev = "${includedir} ${libdir}/lib*${SOLIBSDEV}"
>> +FILES_libbz2-dev = "${includedir} ${libdir}/lib*${SOLIBSDEV} ${libdir}/lib*.la"
>> SECTION_libbz2-dev = "devel"
>> RDEPENDS_libbz2-dev = "libbz2 (= ${EXTENDPKGV})"
>>
>> --
>> 1.7.9.5
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
next prev parent reply other threads:[~2015-04-08 1:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 12:58 [RFC PATCH 0/2] unique -dev package Robert Yang
2015-04-07 12:58 ` [RFC PATCH 1/2] xz: remove xz-dev from PACKAGES Robert Yang
2015-04-07 12:58 ` [RFC PATCH 2/2] bzip2: remove bzip2-dev " Robert Yang
2015-04-08 1:34 ` Khem Raj
2015-04-08 1:55 ` Robert Yang [this message]
2015-04-08 2:10 ` Khem Raj
2015-04-08 2:14 ` Robert Yang
2015-04-07 15:04 ` [RFC PATCH 0/2] unique -dev package Richard Purdie
2016-04-10 22:51 ` Denys Dmytriyenko
2016-04-11 1:19 ` Robert Yang
2016-04-11 1:49 ` Denys Dmytriyenko
2016-04-11 8:35 ` Richard Purdie
2016-04-11 13:42 ` Denys Dmytriyenko
2016-04-11 14:12 ` Gary Thomas
2016-04-11 19:10 ` Denys Dmytriyenko
2016-04-11 19:40 ` Burton, Ross
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=55248AAD.7010503@windriver.com \
--to=liezhi.yang@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