From: Martin Jansa <martin.jansa@gmail.com>
To: "Huang, Jie (Jackie)" <Jackie.Huang@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] xorg-proto-common: allow the empty package
Date: Fri, 3 Jul 2015 12:34:46 +0200 [thread overview]
Message-ID: <20150703103446.GB2436@jama> (raw)
In-Reply-To: <1B858668EC6A94408DCA5225FDFA85AAF11F7479@ALA-MBB.corp.ad.wrs.com>
[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]
On Fri, Jul 03, 2015 at 10:16:09AM +0000, Huang, Jie (Jackie) wrote:
> Thanks for the explanation. I think you’re suggesting that we do nothing for such issue or
> just tell the user to use PN-dev for this kind of packages, right?
Yes, if user wants to install PN-dev, then he should add PN-dev to
IMAGE_INSTALL not PN.
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Friday, July 03, 2015 5:39 PM
> To: Huang, Jie (Jackie)
> Cc: Martin Jansa; OE-core
> Subject: Re: [OE-core] [PATCH] xorg-proto-common: allow the empty package
>
>
> On 3 July 2015 at 10:34, Huang, Jie (Wind River) <jackie.huang@windriver.com<mailto:jackie.huang@windriver.com>> wrote:
>
> 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.
>
> bigreqsproto is development headers. Therefore its in the bigreqsproto-dev package. This is not hard to understand, nor should we start filling the feeds up with empty packages just to please users who can't verify the package names.
>
> Didn't we have this discussion a few months ago? There are some recipes where PN not existing is unusual (avahi was a good example, and I had a partial branch to fix that), but for recipes which entirely consist of development files, there only being a development package is reasonable and predictable.
>
> (If I *had* to do this, I'd have RPROVIDES_${PN}-dev += ${PN})
>
> I see that openssh has similar situation, PN is allowed empty, but it rdepends on “${PN}-scp ${PN}-ssh ${PN}-sshd ${PN}-keygen”.
> That's a different use case entirely: pulling in the entire SSH suite in a single package whilst still allowing resource-constrained or secure systems to pull in only the parts they want.
>
> Ross
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2015-07-03 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 7:52 [PATCH] xorg-proto-common: allow the empty package jackie.huang
2015-07-02 19:39 ` Burton, Ross
2015-07-03 1:34 ` Huang, Jie (Jackie)
2015-07-03 9:04 ` Martin Jansa
2015-07-03 9:13 ` Burton, Ross
2015-07-03 9:34 ` Huang, Jie (Jackie)
2015-07-03 9:38 ` Burton, Ross
2015-07-03 10:16 ` Huang, Jie (Jackie)
2015-07-03 10:26 ` Burton, Ross
2015-07-03 10:34 ` Martin Jansa [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=20150703103446.GB2436@jama \
--to=martin.jansa@gmail.com \
--cc=Jackie.Huang@windriver.com \
--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