All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chong Lu <Chong.Lu@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] dbus: fix a hard dependency about dbus-ptest
Date: Mon, 17 Mar 2014 10:09:28 +0800	[thread overview]
Message-ID: <53265958.6050806@windriver.com> (raw)
In-Reply-To: <232470057.ZuPMps2Ccl@peggleto-mobl5.ger.corp.intel.com>


On 03/14/2014 06:12 PM, Paul Eggleton wrote:
> On Friday 14 March 2014 17:14:27 Chong Lu wrote:
>> On 03/13/2014 06:01 PM, Paul Eggleton wrote:
>>> On Thursday 13 March 2014 17:54:03 Chong Lu wrote:
>>>> On 03/06/2014 06:04 PM, Burton, Ross wrote:
>>>>> On 6 March 2014 08:06, Chong Lu <Chong.Lu@windriver.com> wrote:
>>>>>> +PACKAGES += "dbus-ptest"
>>>>>> +ALLOW_EMPTY_${PN}-ptest = "1"
>>>>>> +RDEPENDS_${PN}-ptest = "${@base_contains('IMAGE_FEATURES',
>>>>>> 'ptest-pkgs',
>>>>>> 'dbus-test-ptest', 'dbus-test', d)}"
>>>>> Clearly I wasn't thinking clearly last week.  You can't check
>>>>> IMAGE_FEATURES in a non-image recipe so this isn't a good solution.
>>>> Do you have any suggestion about this issue?
>>>> If we don't check IMAGE_FEATURES, I have no way to resolve this problem
>>>> that only build but not install ptest. I'm very confused.
>>> This should check DISTRO_FEATURES, not IMAGE_FEATURES. Assuming ptest is
>>> in
>>> DISTRO_FEATURES, even if ptest is not in IMAGE_FEATURES it doesn't matter
>>> if the dependency between dbus-ptest and dbus-ptest-ptest exists because
>>> dbus- ptest itself shouldn't be in the image, so dbus-ptest-ptest
>>> shouldn't be pulled in either. Does that make sense?
>>>
>>> Cheers,
>>> Paul
>> Hi Paul,
>>
>> Thanks for your reply!
>> But I still have a question.
>>
>> I try to following way:
>>
>> # git diff
>> diff --git a/meta/recipes-core/dbus/dbus-ptest_1.6.18.bb
>> b/meta/recipes-core/dbus/dbus-ptest_1.6.18.bb
>> index bc260de..50dfe54 100644
>> --- a/meta/recipes-core/dbus/dbus-ptest_1.6.18.bb
>> +++ b/meta/recipes-core/dbus/dbus-ptest_1.6.18.bb
>> @@ -9,6 +9,7 @@ DEPENDS = "python-pygobject dbus dbus-glib"
>>
>>    RDEPENDS_${PN} += "make"
>>    RDEPENDS_${PN}-dev = ""
>> +ALLOW_EMPTY_${PN} = "1"
>>
>>    SRC_URI = "http://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.gz \
>>               file://tmpdir.patch \
>> diff --git a/meta/recipes-core/dbus/dbus.inc
>> b/meta/recipes-core/dbus/dbus.inc
>> index 677ff78..ba7f3cb 100644
>> --- a/meta/recipes-core/dbus/dbus.inc
>> +++ b/meta/recipes-core/dbus/dbus.inc
>> @@ -6,7 +6,7 @@ LICENSE = "AFL-2 | GPLv2+"
>>    LIC_FILES_CHKSUM = "file://COPYING;md5=10dded3b58148f3f1fd804b26354af3e \
>> file://dbus/dbus.h;beginline=6;endline=20;md5=7755c9d7abccd5dbd25a6a974538bb
>> 3c" DEPENDS = "expat virtual/libintl"
>> -RDEPENDS_dbus = "${@base_contains('DISTRO_FEATURES', 'ptest',
>> 'dbus-ptest-ptest', '', d)}"
>> +RDEPENDS_dbus = "dbus-ptest"
> The line above is the problem. You *cannot* do this or dbus-ptest (and
> therefore dbus-ptest-ptest) will always be installed whether you want it or
> not. You need to remove this line.
>
> Cheers,
> Paul
>
Hi Paul,

Do you mean the patch we only need to remove RDEPENDS_dbus = 
"${@base_contains('DISTRO_FEATURES', 'ptest', 'dbus-ptest-ptest', '', 
d)}" in dbus.inc ?
If do this, we can't build and install dbus-ptest through `bitbake dbus' 
command.
How to relate between dbus and dbus-ptest?

Best Regards
Chong



  reply	other threads:[~2014-03-17  2:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  8:06 [PATCH 0/1] dbus: fix a hard dependency about dbus-ptest Chong Lu
2014-03-06  8:06 ` [PATCH 1/1] " Chong Lu
2014-03-06 10:04   ` Burton, Ross
2014-03-07  2:13     ` Chong Lu
2014-03-10 11:51       ` Burton, Ross
2014-03-13  9:54     ` Chong Lu
2014-03-13 10:01       ` Paul Eggleton
2014-03-13 10:48         ` Paul Eggleton
2014-03-14  9:14         ` Chong Lu
2014-03-14 10:12           ` Paul Eggleton
2014-03-17  2:09             ` Chong Lu [this message]
2014-03-17 10:44               ` Paul Eggleton
2014-03-17 11:05                 ` Paul Eggleton
2014-03-18  7:12                   ` Chong Lu

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=53265958.6050806@windriver.com \
    --to=chong.lu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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 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.