Bug 6937

Summary:	install package "postinst-intercept pointercal-xinput oprofileui avahi" to image failed
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Hongxu Jia <hongxu.jia>
Component:	core	Assignee:	Hongxu Jia <hongxu.jia>
Status:	RESOLVED NOTABUG	QA Contact:
Severity:	normal
Priority:	Medium	CC:	liezhi.yang, meta.mr.watcher, meta.watcher, richard.purdie, sgw
Version:	1.8
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Hongxu Jia 2014-11-07 07:04:58 UTC

vim local.conf
...
IMAGE_INSTALL_append = " postinst-intercept pointercal-xinput oprofileui avahi"
...

bitbake core-image-minimal
...
ERROR: avahi not found in the base feeds (qemux86_64 core2-64 x86_64 noarch any all).
...

Here is the analysis:
1. postinst-intercept is only used for nativesdk, so the
postinst-interceptshould be invalid at the recipe parasing
time. We could rename the recipe to nativesdk-postinst-intercept

2. pointercal-xinput is conditionally install file if it
has a contents, so it should allow the package empty.

3. use oprofileui-viewer as oprofileui's provider

4. use avahi-daemon as avahi's provider

Comment 1 Richard Purdie 2015-03-26 09:44:41 UTC

Firstly, its not a reasonable expectation that every recipe name can be added to IMAGE_INSTALL and have things "work". This simply isn't the way the system has been designed. If that is an issue I'd like to understand where the requirement has come from.

The postinst issue was dealt with in http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=0f5d0e98f6b77a768ee6b77646d0351401d49f0d

The pointercal issue is deliberate as pointed out on the mailing list:

http://git.openembedded.org/meta-openembedded/commit/?id=9477e53e8a8ffde17b558ac436550687db4b86a0

and is meant to be installed as a RRECOMMEND. There is little point in generating a package just for the sake of it.

For avahi and oprofileui, the main packages are simply empty. I'm wondering if we should put a PACKAGES_remove = "${PN}" into those recipes so that those packages aren't generated?

Comment 2 Richard Purdie 2015-03-26 09:59:40 UTC

Moving to M1, we have a simple plan here for two simple patches and can then get this closed.

Comment 3 Hongxu Jia 2016-07-29 02:19:04 UTC

It is not a bug, you can't install recipe to image, but only package should
be installed.