From: Hongxu Jia <hongxu.jia@windriver.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/4] avahi.inc: use avahi-daemon as avahi's provider
Date: Tue, 11 Nov 2014 17:19:04 +0800 [thread overview]
Message-ID: <5461D488.1050304@windriver.com> (raw)
In-Reply-To: <3313D76B-7622-4F78-B550-E3BAD5910B4A@dominion.thruhere.net>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
On 11/11/2014 05:02 PM, Koen Kooi wrote:
> It is not a bug when recipe foo.bb doesn't generate foo.ipk. Your changes introduce needless churn and break upgrade paths only to cater to people making wrong assumptions.
Except on purpose to not generate recipe_name package, the other
situation is indeed a bug, such as ssmping and pimd, it don't generate
any package at all.
http://cgit.openembedded.org/meta-openembedded/commit/?id=4b6970c24c3fb0926fd700678c0e11de43a5bf92
http://cgit.openembedded.org/meta-openembedded/commit/?id=c5398fc0fe246e4828c9e950f779f437266bfaa1
If the "Your chagnes" means add checking about the non-create
package, I think you are right, many recipe don't want generate
recipe_name package on purpose, we should avoid that noisy
warning, maybe we should add a script to do that on the result of
world build.
But if the "Your chagnes" means the above fix, I think these fixes is
reasonable for users, especially for newbies. (Actually the issues
were reported by our customer)
//Hongxu
[-- Attachment #2: Type: text/html, Size: 2052 bytes --]
next prev parent reply other threads:[~2014-11-11 9:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 7:57 [PATCH 0/4] fix install package "postinst-intercept pointercal-xinput oprofileui avahi" to image failed Hongxu Jia
2014-11-07 7:57 ` [PATCH 1/4] avahi.inc: use avahi-daemon as avahi's provider Hongxu Jia
2014-11-07 14:38 ` Martin Jansa
2014-11-07 14:42 ` Burton, Ross
2014-11-08 2:31 ` Hongxu Jia
2014-11-08 18:53 ` Koen Kooi
2014-11-10 2:02 ` Hongxu Jia
2014-11-10 6:42 ` Martin Jansa
2014-11-10 7:35 ` Hongxu Jia
2014-11-11 9:02 ` Koen Kooi
2014-11-11 9:19 ` Hongxu Jia [this message]
2014-11-07 7:57 ` [PATCH 2/4] oprofileui: use oprofileui-viewer as oprofileui's provider Hongxu Jia
2014-11-07 12:06 ` Burton, Ross
2014-11-07 14:47 ` Burton, Ross
2014-11-08 9:20 ` Hongxu Jia
2014-11-07 7:57 ` [PATCH 3/4] pointercal-xinput: add the missing ALLOW_EMPTY Hongxu Jia
2014-11-07 14:43 ` Martin Jansa
2014-11-07 7:57 ` [PATCH 4/4] postinst-intercept: rename recipe for nativesdk only Hongxu Jia
[not found] ` <CALbNGRTsV6udERwG8XBoxuoFVqeyexwM46-u1Ot__AFBD_TAUg@mail.gmail.com>
[not found] ` <545C826F.6050002@windriver.com>
2014-11-07 9:28 ` Andreas Müller
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=5461D488.1050304@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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