From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Ship dbus config and dbus service activation files
Date: Thu, 11 Dec 2008 06:31:21 -0600 [thread overview]
Message-ID: <49410819.6040302@dls.net> (raw)
In-Reply-To: <ghqgho$r9j$1@ger.gmane.org>
Koen Kooi rudely writes:
> On 11-12-08 01:55, Mike (mwester) wrote:
>
> http://www.angstrom-distribution.org/repo/?pkgname=dbus-1
> http://www.angstrom-distribution.org/repo/?pkgname=libdbus-1-3
>
> Now where do you see it the _packages_ depending on libx11-6? Is dbus
> going to be the new python where everybody starts screaming about
> requiring X at runtime, when it's only a buildtime dep to build an
> *optional* subpackage like python-tk? Please stop with the FUD.
dbus-1 recommends dbus-x11, dbus-x11 depends libx11-6 (and other X libs).
So there you go, opkg install <anything-depending-on-dbus> blows up your
flash space by pulling in numerous X libs. No FUD - very real concern.
(But if it's not a concern for Angstrom, then fine -- please ignore
this issue; if I fix it, I'll make sure that it won't change for Angstrom.)
Regards
Mike (mwester)
next prev parent reply other threads:[~2008-12-11 12:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 23:49 [RFC] Ship dbus config and dbus service activation files Stefan Schmidt
2008-12-11 0:16 ` Thomas Kunze
2008-12-11 0:33 ` Stefan Schmidt
2008-12-11 13:29 ` Stefan Schmidt
2008-12-11 0:37 ` Michael 'Mickey' Lauer
2008-12-11 0:55 ` Mike (mwester)
2008-12-11 1:07 ` Michael 'Mickey' Lauer
2008-12-11 7:48 ` Koen Kooi
2008-12-11 7:47 ` Koen Kooi
2008-12-11 12:31 ` Mike (mwester) [this message]
2008-12-11 12:42 ` Koen Kooi
2008-12-11 12:45 ` Koen Kooi
2008-12-11 13:06 ` Andrea Adami
2008-12-11 13:31 ` Stefan Schmidt
2008-12-11 8:45 ` Koen Kooi
2008-12-11 9:37 ` Andrea Adami
2008-12-11 10:07 ` Koen Kooi
2008-12-11 13:22 ` Stefan Schmidt
2008-12-11 13:38 ` Graeme Gregory
2008-12-11 13:55 ` Stefan Schmidt
2008-12-11 14:33 ` Graeme Gregory
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=49410819.6040302@dls.net \
--to=mwester@dls.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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