I see your point, I think we can make the empty PN rdepends on PN-dev(but the
dev-deps QA check need to be skipped),
then when user try to add PN, PN-dev will also be installed, so it’s not an
useless empty package.
I see that openssh has similar situation, PN is allowed empty, but it rdepends
on “${PN}-scp ${PN}-ssh ${PN}-sshd ${PN}-keygen”.
Does it make sense to you?
Thanks,
Jackie
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Friday, July 03, 2015 5:14 PM
To: Martin Jansa
Cc: Huang, Jie (Jackie); OE-core
Subject: Re: [OE-core] [PATCH] xorg-proto-common: allow the empty package
On 3 July 2015 at 10:04, Martin Jansa
<martin.ja...@gmail.com<mailto:martin.ja...@gmail.com>> wrote:
I as a customer would definitely prefer error message even later in the
build then getting completely useless empty package installed in my
image and blame you for installing it when I was expecting to find
bigreqsproto in my rootfs.
Agreed. Installing bigreqsproto and not getting anything is far more annoying
than the error and following epiphany that if you want the development headers
for bigreqsproto you should install bigreqsproto-dev.
Ross
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
