From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Ship dbus config and dbus service activation files
Date: Wed, 10 Dec 2008 18:55:39 -0600 [thread overview]
Message-ID: <4940650B.1000802@dls.net> (raw)
In-Reply-To: <200812110137.01104.mickey@vanille-media.de>
Michael 'Mickey' Lauer wrote:
> We can compile it completely without dbus support in a seperate recipe, if
> that's what you want -- but given the increasing ubiquity of dbus, that
> doesn't make much sense.
Which raises a point -- there are still devices out there that don't
want the X11 libraries (due to flash space limitations) -- perhaps it is
_dbus_ that needs splitting into two separate recipes, one with X and
one without?
I think this would mean that everything would change to depend on
"virtual/dbus", right? -- and that would be a fairly disruptive change,
hence my comments here to see if anyone has strong protests or better ideas.
Mike (mwester)
next prev parent reply other threads:[~2008-12-11 1:00 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) [this message]
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)
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=4940650B.1000802@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 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.