From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] dbus: Ensure dbus-nativesdk doesn't RPROVIDE dbus-x11
Date: Wed, 01 Aug 2012 23:09:22 +0100 [thread overview]
Message-ID: <1343858962.9756.70.camel@ted> (raw)
In-Reply-To: <20120801220318.GL16306@jama.jama.net>
On Thu, 2012-08-02 at 00:03 +0200, Martin Jansa wrote:
> On Wed, Aug 01, 2012 at 10:54:43PM +0100, Richard Purdie wrote:
> > dbus-x11 should not RPROVIDE dbus-x11 as this is incorrect and confuses
> > builds. This fixes the nativesdk case.
> >
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> > diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
> > index 164c4d3..1984c74 100644
> > --- a/meta/recipes-core/dbus/dbus.inc
> > +++ b/meta/recipes-core/dbus/dbus.inc
> > @@ -33,9 +33,12 @@ DEBIANNAME_${PN} = "dbus-1"
> >
> > PACKAGES =+ "${PN}-lib ${PN}-systemd"
> >
> > +OLDPKGNAME = "dbus-x11"
> > +OLDPKGNAME_virtclass-nativesdk = ""
> > +
> > # for compatibility
> > -RPROVIDES_${PN} = "dbus-x11"
> > -RREPLACES_${PN} += "dbus-x11"
> > +RPROVIDES_${PN} = "${OLDPKGNAME}"
> > +RREPLACES_${PN} += "${OLDPKGNAME}"
>
> what about this?
> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/026947.html
They're each different ways to fix the problem. The above just kills the
nativesdk version since I don't think anyone will feel strongly about it
but I don't have strong feelings. I notice Marcin also has a patch out,
for some reason I didn't see that initially :(.
Cheers,
Richard
prev parent reply other threads:[~2012-08-01 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 21:54 [PATCH] dbus: Ensure dbus-nativesdk doesn't RPROVIDE dbus-x11 Richard Purdie
2012-08-01 22:03 ` Martin Jansa
2012-08-01 22:09 ` Richard Purdie [this message]
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=1343858962.9756.70.camel@ted \
--to=richard.purdie@linuxfoundation.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