From: Phil Blundell <pb@pbcl.net>
To: Kai Kang <kai.kang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] eglibc-dbg: provides libc6-dbg
Date: Wed, 22 Jan 2014 07:08:10 +0000 [thread overview]
Message-ID: <1390374490.24755.2.camel@e130.pbcl.net> (raw)
In-Reply-To: <1390360372-10947-1-git-send-email-kai.kang@windriver.com>
On Wed, 2014-01-22 at 11:12 +0800, Kai Kang wrote:
> Update eglibc-package.inc to let eglibc-dbg provides libc6-dbg.
>
> The use case is that when libc6-dbg is needded to be installed into
> image, we don't need change glibc-dbg to uclibc-dbg in recipe when we
> change to use package uclibc as default C library.
> -RPROVIDES_${PN}-dbg = "glibc-dbg"
> +RPROVIDES_${PN}-dbg = "glibc-dbg libc6-dbg"
Isn't PKG_${PN}-dbg set to libc6-dbg anyway (by libc-common.bbclass)?
Can you explain the use case and justification for this change a bit
more clearly?
p.
next prev parent reply other threads:[~2014-01-22 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 3:12 [PATCH] eglibc-dbg: provides libc6-dbg Kai Kang
2014-01-22 7:08 ` Phil Blundell [this message]
2014-01-22 9:06 ` Kang Kai
2014-01-25 19:30 ` Phil Blundell
2014-01-27 3:20 ` Kang Kai
2014-01-27 11:25 ` Phil Blundell
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=1390374490.24755.2.camel@e130.pbcl.net \
--to=pb@pbcl.net \
--cc=kai.kang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.