[OE-core] [PATCH] xorg-proto-common: allow the empty package

[Huang, Jie (Jackie)]

Yeah I know it’s not good to have the empty package and we can remove dependencies to void error, but
our customer may add the package through IMAGE_INSTALL in local.conf and blame it fails until do_rootfs:

ERROR: bigreqsproto not found in the base feeds (intel_x86_64 core2-64 x86_64 noarch any all).

Do we have a way to find out a PN package is empty at an earlier time so that we may warn the user not
to add this package into image?

Thanks,
Jackie

From: Burton, Ross [mailto:ross.burton at intel.com]
Sent: Friday, July 03, 2015 3:40 AM
To: Huang, Jie (Jackie)
Cc: OE-core
Subject: Re: [OE-core] [PATCH] xorg-proto-common: allow the empty package


On 1 July 2015 at 08:52, <jackie.huang at windriver.com<mailto:jackie.huang at windriver.com>> wrote:
 # ${PN} is empty so we need to tweak -dev and -dbg package dependencies
+# and allow ${PN} to be created empty
+ALLOW_EMPTY_${PN} = "1"
 RDEPENDS_${PN}-dev = ""
 RRECOMMENDS_${PN}-dbg = "${PN}-dev (= ${EXTENDPKGV})"

As the comment and surrounding lines state, the dependencies on PN from PN-dev and PN-dbg are already removed.  What other package has a runtime dependency on PN, and when you find it a better solution is to remove the dependency instead of creating empty packages.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150703/72daa8d5/attachment-0002.html>