Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jian Liu <jian.liu@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] linux-libc-headers: not to create empty rpm
Date: Wed, 20 Jan 2016 16:20:47 +0800	[thread overview]
Message-ID: <569F435F.7030208@windriver.com> (raw)
In-Reply-To: <1453276179.27999.139.camel@linuxfoundation.org>


On 2016年01月20日 15:49, Richard Purdie wrote:
> On Wed, 2016-01-20 at 14:10 +0800, Jian Liu wrote:
>> linux-libc-headers-dbg is empty and unset ALLOW_EMPTY
>> for this sub-package.
>>
>> Signed-off-by: Jian Liu <jian.liu@windriver.com>
>>
>> diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc
>> -headers.inc b/meta/recipes-kernel/linux-libc-headers/linux-libc
>> -headers.inc
>> index 2ba6ed5..75f6899 100644
>> --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc
>> +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc
>> @@ -76,3 +76,5 @@ RRECOMMENDS_${PN}-dbg = "${PN}-dev (=
>> ${EXTENDPKGV})"
>>   
>>   INHIBIT_DEFAULT_DEPS = "1"
>>   DEPENDS += "unifdef-native"
>> +
>> +ALLOW_EMPTY_${PN}-dbg = "0"
> It may be empty but our packaging criteria say we always generate a dbg
> package since they can be part of dependency chains and we're
> interested in the dependencies.
>
> I appreciate in this case, the libc-headers are a corner case at the
> end of the chains so you could argue this one can be skipped for
> packaging but the system does assume all -dbg packages exist so I'd
> prefer to leave this alone, unless its part of a bigger picture rethink
> about -dbg packages.
I see

Thanks very much for reminding me this.

>
> Cheers,
>
> Richard
>
>
>



      reply	other threads:[~2016-01-20  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20  6:10 [PATCH] linux-libc-headers: not to create empty rpm Jian Liu
2016-01-20  7:49 ` Richard Purdie
2016-01-20  8:20   ` Jian Liu [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=569F435F.7030208@windriver.com \
    --to=jian.liu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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