From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 18/20] eglibc: refactor packages for staticdev
Date: Sun, 22 Jan 2012 20:30:21 +0000 [thread overview]
Message-ID: <1327264221.2859.2.camel@pb-ThinkPad-R50e> (raw)
In-Reply-To: <4236e557f38c0e4c3e7088fd528face5b74f60a8.1327123057.git.sgw@linux.intel.com>
On Fri, 2012-01-20 at 21:18 -0800, Saul Wold wrote:
> @@ -54,6 +56,7 @@ RDEPENDS_${PN}-utils += "bash"
> FILES_${PN}-pcprofile = "${base_libdir}/libpcprofile.so"
> FILES_eglibc-thread-db${PKGSUFFIX} = "${base_libdir}/libthread_db.so.* ${base_libdir}/libthread_db-*.so"
> RPROVIDES_${PN}-dev += "libc-dev"
> +RPROVIDES_${PN}-dev += "libc-staticdev"
Is that really what you wanted?
More generally, I'm not very convinced that all these RPROVIDES in the
eglibc recipes are serving any useful purpose anymore. I think we
should be trying to get rid of them, not adding new ones. Does anybody
know of anything which currently depends on them?
p.
next prev parent reply other threads:[~2012-01-22 20:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 5:18 [PATCH 00/20] Refactor -dev packages to move *.a to -staticdev packages Saul Wold
2012-01-21 5:18 ` [PATCH 01/20] Fix Upstream-Status entries Saul Wold
2012-01-21 5:18 ` [PATCH 02/20] apmd: refactor packages for staticdev Saul Wold
2012-01-21 5:18 ` [PATCH 03/20] avahi-ui: " Saul Wold
2012-01-21 5:18 ` [PATCH 04/20] augeas: " Saul Wold
2012-01-21 5:18 ` [PATCH 05/20] libsoup: " Saul Wold
2012-01-21 5:18 ` [PATCH 06/20] sysfsutils: " Saul Wold
2012-01-21 5:18 ` [PATCH 07/20] libxft: " Saul Wold
2012-01-21 5:18 ` [PATCH 08/20] sqlite3: " Saul Wold
2012-01-21 5:18 ` [PATCH 09/20] apr-util: " Saul Wold
2012-01-21 5:18 ` [PATCH 10/20] mpeg2dec: " Saul Wold
2012-01-21 5:18 ` [PATCH 11/20] tiff: " Saul Wold
2012-01-21 5:18 ` [PATCH 12/20] gstreamer: " Saul Wold
2012-01-21 5:18 ` [PATCH 13/20] libtool: " Saul Wold
2012-01-27 8:21 ` Koen Kooi
2012-01-21 5:18 ` [PATCH 14/20] syslinux: " Saul Wold
2012-01-21 5:18 ` [PATCH 15/20] tcp-wrappers: " Saul Wold
2012-01-21 5:18 ` [PATCH 16/20] opkg: move common code & metadata into opkg.inc to reduce code duplication Saul Wold
2012-01-21 6:13 ` Otavio Salvador
2012-01-23 16:21 ` Saul Wold
2012-01-21 5:18 ` [PATCH 17/20] opkg: refactor packages for staticdev Saul Wold
2012-01-21 5:18 ` [PATCH 18/20] eglibc: " Saul Wold
2012-01-22 20:30 ` Phil Blundell [this message]
2012-01-23 16:28 ` Saul Wold
2012-01-21 5:18 ` [PATCH 19/20] binutils: " Saul Wold
2012-01-21 5:18 ` [PATCH 20/20] gcc: " Saul Wold
2012-01-22 20:40 ` 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=1327264221.2859.2.camel@pb-ThinkPad-R50e \
--to=philb@gnu.org \
--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