Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Chong Lu <Chong.Lu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] dbus: fix a hard dependency about dbus-ptest
Date: Fri, 7 Mar 2014 10:13:09 +0800	[thread overview]
Message-ID: <53192B35.3060807@windriver.com> (raw)
In-Reply-To: <CAJTo0LZ_OjXVhoNv6wk085=5vY=i64_8T6s=Tef5h7qgFC5Sfw@mail.gmail.com>


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)}"
> Nice idea, but wouldn't a more correct solution be to have dbus-ptest
> added to PACKAGES conditionally (instead of always generating
> dbus-ptest and conditionally adding the dependency)?
>
> Ross
>
>
Hi Ross,

Do you mean using PACKAGES += "${@base_contains('IMAGE_FEATURES', 
'ptest-pkgs', 'dbus-ptest-ptest', 'dbus-ptest', d)}" or something else?


Best Regards
Chong


  reply	other threads:[~2014-03-07  2:13 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 [this message]
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
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=53192B35.3060807@windriver.com \
    --to=chong.lu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox