From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Zhenbo Gao <zhenbo.gao@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] connman: add alias for connman
Date: Wed, 25 May 2016 09:05:36 +0100 [thread overview]
Message-ID: <1464163536.9570.92.camel@linuxfoundation.org> (raw)
In-Reply-To: <1464160265-16527-1-git-send-email-zhenbo.gao@windriver.com>
On Wed, 2016-05-25 at 15:11 +0800, Zhenbo Gao wrote:
> connman get conflicts with networkmanager when building
> the project.
>
> here introduce alias virtual/networkmanager for these
> two recipes, so setting PREFERRED_PROVIDER to the proper
> one can solve the conflicts.
>
> this patch is for connman recipe.
We do not use the virtual/* namespace in package dependencies, only in
the build time DEPENDS/PROVIDES space. This is because there is no way
to indicate how the package manager should resolve such things amongst
many other reasons.
Cheers,
Richard
next prev parent reply other threads:[~2016-05-25 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 7:11 [PATCH] connman: add alias for connman Zhenbo Gao
2016-05-25 8:05 ` Andreas Oberritter
2016-05-25 8:05 ` Richard Purdie [this message]
2016-05-25 9:41 ` zhenbo
2016-05-25 10:34 ` Burton, Ross
2016-05-25 8:30 ` Burton, Ross
2016-05-25 9:15 ` zhenbo
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=1464163536.9570.92.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=zhenbo.gao@windriver.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