From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: dbus-native --with-x
Date: Wed, 01 Jun 2011 17:03:55 +0100 [thread overview]
Message-ID: <1306944235.2529.109.camel@phil-desktop> (raw)
In-Reply-To: <1306944074.2529.107.camel@phil-desktop>
On Wed, 2011-06-01 at 17:01 +0100, Phil Blundell wrote:
> Is there any compelling reason why dbus-native needs to be built
> --with-x? This seems to be causing quite a large stack of native X11
> packages to get built with, as far as I can tell, no useful result.
Oh, on the subject of out-of-control dependency chains, my other pet
bugbear at the moment is rpm-native:
"rpm-native" -> "bzip2-native"
"rpm-native" -> "db-native"
"rpm-native" -> "perl-native"
"rpm-native" -> "openssl-native"
"rpm-native" -> "expat-native"
"rpm-native" -> "autoconf-native"
"rpm-native" -> "automake-native"
"rpm-native" -> "libtool-native"
"rpm-native" -> "gnu-config-native"
"rpm-native" -> "gettext-native"
"rpm-native" -> "python-native"
"rpm-native" -> "acl-native"
"rpm-native" -> "elfutils-native"
"rpm-native" -> "libpcre-native"
"rpm-native" -> "zlib-native"
"rpm-native" -> "popt-native"
"rpm-native" -> "attr-native"
As far as I can tell, the native rpm is never being used in any way
which requires it to have openssl, and I suspect the same is probably
true for some of the other libs above. Does anybody happen to know what
features rpm-native actually requires for correct operation?
p.
next prev parent reply other threads:[~2011-06-01 16:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 16:01 dbus-native --with-x Phil Blundell
2011-06-01 16:03 ` Phil Blundell [this message]
2011-06-01 16:11 ` Koen Kooi
2011-06-01 16:16 ` Phil Blundell
2011-06-01 16:48 ` Mark Hatle
2011-06-01 16:54 ` Phil Blundell
2011-06-01 16:58 ` Mark Hatle
2011-06-01 17:08 ` Phil Blundell
2011-06-01 18:55 ` rpmdeps, was " Mark Hatle
2011-06-01 19:00 ` Koen Kooi
2011-06-01 21:14 ` Mark Hatle
2011-06-01 20:02 ` Phil Blundell
2011-06-01 21:17 ` Mark Hatle
2011-06-02 9:18 ` Phil Blundell
2011-06-01 20:22 ` Phil Blundell
2011-06-01 22:00 ` Tom Rini
2011-06-01 22:07 ` Henning Heinold
2011-06-01 22:22 ` Tom Rini
2011-06-01 22:38 ` Mark Hatle
2011-06-02 9:08 ` Phil Blundell
2011-06-02 17:04 ` Tom Rini
2011-06-02 19:21 ` Phil Blundell
2011-06-02 19:29 ` Tom Rini
2011-06-02 7:12 ` Phil Blundell
2011-06-01 16:10 ` Koen Kooi
2011-06-01 16: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=1306944235.2529.109.camel@phil-desktop \
--to=pb@pbcl.net \
--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