From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] dbus: include dbus-launch in the main dbus package
Date: Wed, 25 Jul 2012 15:23:02 +0100 [thread overview]
Message-ID: <1528039.fg9dttDzQG@helios> (raw)
In-Reply-To: <CAJTo0LbFcZYhBzgO4wEhnS4Dq+msQP9pu8Biagiy3cPGUoPGkA@mail.gmail.com>
On Wednesday 25 July 2012 15:19:10 Burton, Ross wrote:
> On 25 July 2012 15:17, Koen Kooi <koen@dominion.thruhere.net> wrote:
> > This breaks the upgrade path
>
> So how would the upgrade path be unbroken? A dummy dbus-x11 package
> that pulls in dbus, I suspect.
RREPLACES_${PN} += "dbus-x11" ought to be enough...
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-25 14:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 14:03 [PATCH] dbus: include dbus-launch in the main dbus package Radu Moisan
2012-07-25 13:58 ` Phil Blundell
2012-07-25 14:16 ` Koen Kooi
2012-07-25 14:17 ` Koen Kooi
2012-07-25 14:19 ` Burton, Ross
2012-07-25 14:23 ` Paul Eggleton [this message]
2012-07-25 14:24 ` Burton, Ross
2012-07-25 14:49 ` Koen Kooi
-- strict thread matches above, loose matches on Subject: below --
2012-07-30 11:24 Radu Moisan
2012-07-30 15:07 ` Burton, Ross
2012-07-31 5:39 ` Radu Moisan
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=1528039.fg9dttDzQG@helios \
--to=paul.eggleton@linux.intel.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.