From: Chong Lu <Chong.Lu@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 1/1] perf: fix issue about package splitting
Date: Thu, 4 Sep 2014 16:17:52 +0800 [thread overview]
Message-ID: <54082030.2090009@windriver.com> (raw)
In-Reply-To: <1409818215.12482.20.camel@ted>
On 09/04/2014 04:10 PM, Richard Purdie wrote:
> On Thu, 2014-09-04 at 16:06 +0800, Chong Lu wrote:
>> On 09/04/2014 03:27 PM, Chong Lu wrote:
>>> On 09/03/2014 06:42 PM, Richard Purdie wrote:
>>>> On Wed, 2014-09-03 at 17:05 +0800, Chong Lu wrote:
>>>>> Currently, perf can't split to perf-archive, perf-tests, perf-python
>>>>> and
>>>>> perf-perl. All files are included in perf package. Change the files
>>>>> paths to
>>>>> make split successfully and add PACKAGECONFIG to make main pkg
>>>>> depends on sub
>>>>> pkgs as default.
>>>>>
>>>>> Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
>>>>> ---
>>>>> meta/recipes-kernel/perf/perf.bb | 17 ++++++++++++-----
>>>>> 1 file changed, 12 insertions(+), 5 deletions(-)
>>>>>
>>>>> diff --git a/meta/recipes-kernel/perf/perf.bb
>>>>> b/meta/recipes-kernel/perf/perf.bb
>>>>> index bfd210c..baf0077 100644
>>>>> --- a/meta/recipes-kernel/perf/perf.bb
>>>>> +++ b/meta/recipes-kernel/perf/perf.bb
>>>>> @@ -149,20 +149,27 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
>>>>> PACKAGES =+ "${PN}-archive ${PN}-tests ${PN}-perl ${PN}-python"
>>>>> +PACKAGECONFIG ??= "archive perl python tests"
>>>>> +PACKAGECONFIG[archive] = ",,, ${PN}-archive"
>>>>> +PACKAGECONFIG[perl] = ",,, ${PN}-perl"
>>>>> +PACKAGECONFIG[python] = ",,, ${PN}-python"
>>>>> +PACKAGECONFIG[tests] = ",,, ${PN}-tests"
>>>>> +
>>>>> RDEPENDS_${PN} += "elfutils"
>>>>> RDEPENDS_${PN}-archive =+ "bash"
>>>>> RDEPENDS_${PN}-python =+ "bash python"
>>>>> RDEPENDS_${PN}-perl =+ "bash perl perl-modules"
>>>>> +RDEPENDS_${PN}-tests =+ "python"
>>>> I now realise the trick you're playing with PACKAGECONFIG here. Instead
>>>> can we just define a package (say ${PN}-all but I'll accept a better
>>>> name) which has dependencies on archive perl python tests so then the
>>>> user can choose ${PN}, ${PN}-all or some other combination depending on
>>>> their needs?
>>> OK, I will put archive perl python and tests in ${PN}-full.
>> Sorry, I don't think we should use a pkg include four sub pkgs.
>> We have perf_feature_enabled to control whether enable perl and python,
>> so it is hard to use feature if we put four sub pkgs in one pkg.
> This isn't what I meant. I meant add a ${PN}-full package which
> RDEPENDS_${PN}-full = "${PN}-archive ${PN}-python ${PN}-perl
> ${PN}-tests"
Do you mean I should use:
PACKAGECONFIG ??= "full"
PACKAGECONFIG[full] = ",,, ${PN}-full"
RDEPENDS_${PN}-full = "${PN}-archive ${PN}-python ${PN}-perl ${PN}-tests"
Best Regards
Chong
> Cheers,
>
> Richard
>
>
>
>
>
next prev parent reply other threads:[~2014-09-04 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 9:05 [PATCH V2 0/1] perf: fix issue about package splitting Chong Lu
2014-09-03 9:05 ` [PATCH V2 1/1] " Chong Lu
2014-09-03 10:42 ` Richard Purdie
2014-09-04 7:27 ` Chong Lu
2014-09-04 8:06 ` Chong Lu
2014-09-04 8:10 ` Richard Purdie
2014-09-04 8:17 ` Chong Lu [this message]
2014-09-04 8:24 ` Richard Purdie
2014-09-04 8:07 ` Richard Purdie
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=54082030.2090009@windriver.com \
--to=chong.lu@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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