From: Yi Zhao <yi.zhao@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"Burton, Ross" <ross.burton@intel.com>
Cc: Yue Tao <yue.tao@windriver.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] randrproto: set ALLOW_EMPTY
Date: Wed, 6 Jul 2016 17:16:08 +0800 [thread overview]
Message-ID: <577CCC58.4000402@windriver.com> (raw)
In-Reply-To: <1467795297.8590.208.camel@linuxfoundation.org>
Hi Ross & Richard,
So that's a wrong usage for adding this package to an image.
Thank you for the explanation.
Yi
在 2016年07月06日 16:54, Richard Purdie 写道:
> On Wed, 2016-07-06 at 09:41 +0100, Burton, Ross wrote:
>> On 6 July 2016 at 09:09, Yi Zhao <yi.zhao@windriver.com> wrote:
>>> When adding package randrproto to an image with
>>> IMAGE_INSTALL_append = " randrproto", an error occurs:
>>>
>>> $ bitbake core-image-sato
>>> [snip]
>>> ERROR: randrproto not found in the base feeds (qemux86 i586 x86
>>> noarch any all).
>>> [snip]
>>>
>> No.
>>
>> $ oe-pkgdata-util list-pkgs -rp randrproto
>> randrproto-dbg
>> randrproto-dev
>> randrproto-doc
>>
>> The answer here is to not add randrproto to an image, as the package
>> doesn't exist. Especially when this is whack-a-mole:
>>
>> $ oe-pkgdata-util list-pkgs -rp renderproto
>> renderproto-dev
>> renderproto-dbg
>> renderproto-doc
>>
>> (repeat for every recipe in x11-proto)
> Agreed. We've seen patches like this before, we rejected them last time
> and we will do again.
>
> Cheers,
>
> Richard
>
prev parent reply other threads:[~2016-07-06 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 8:09 [PATCH 0/1] randrproto: set ALLOW_EMPTY Yi Zhao
2016-07-06 8:09 ` [PATCH 1/1] " Yi Zhao
2016-07-06 8:41 ` Burton, Ross
2016-07-06 8:54 ` Richard Purdie
2016-07-06 9:16 ` Yi Zhao [this message]
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=577CCC58.4000402@windriver.com \
--to=yi.zhao@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@intel.com \
--cc=yue.tao@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