From: Radu Moisan <radu.moisan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] dbus: include dbus-launch in the main dbus package
Date: Thu, 26 Jul 2012 15:36:50 +0300 [thread overview]
Message-ID: <501139E2.1020003@intel.com> (raw)
In-Reply-To: <CAJTo0LZx5E7tcvLUMrjPdH2B5p+DnFxU63tbtL6tsDX5dVfVSQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
I understand the reasoning behind RPROVIDES. I've grep'ed the sources
and none of the packages that depend on dbus-x11 have build time
dependencies on it, so the question arises "what's the point of
PROVIDES?". I understand the compatibility argument, but it seems to me
more like an argument when dependencies are not clear, but in this case
they are clear. The following packages depend on dbus-x11, at run-time:
radu@dell-desktop>grep . -re dbus-x11
./recipes-bsp/qemu-config/*qemu-config.bb*:RDEPENDS_${PN} = "distcc
${@base_contains('DISTRO_FEATURES', 'x11', 'dbus-x11', '', d)}
task-core-nfs-server oprofileui-server rsync bash"
./recipes-gnome/gnome/*gconf_3.2.3.bb*:RDEPENDS_${PN} +=
"${@base_contains('DISTRO_FEATURES', 'x11', 'dbus-x11', '', d)}"
./recipes-graphics/x11-common/*x11-common_0.1.bb*:RDEPENDS_${PN} =
"dbus-x11 xmodmap xdpyinfo xtscal xinit formfactor"
Rephrasing my question, what would happen (potentially bad) if I don't
have PROVIDES="dbus-x11" line in my recipe?
Also, I've done a clean build without PROVIDES="dbus-x11" line in
dbus.inc and the build finished successfully, as if it were there (tried
that as well).
Radu
On 07/26/2012 03:00 PM, Burton, Ross wrote:
> On 26 July 2012 12:55, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> It would be nice if other layers that have RDEPENDS_foo = "dbus-x11" keep working till their maintainers get around fixing them. Note that you might need to do a -c cleansstate on dbus first to trigger any errors.
> Yes, and isn't that what the RPROVIDES is for?
[-- Attachment #2: Type: text/html, Size: 2429 bytes --]
next prev parent reply other threads:[~2012-07-26 12:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 6:17 [PATCH v3] dbus: include dbus-launch in the main dbus package Radu Moisan
2012-07-26 6:29 ` Radu Moisan
2012-07-26 8:08 ` Koen Kooi
2012-07-26 8:42 ` Paul Eggleton
2012-07-26 8:43 ` Koen Kooi
2012-07-26 9:18 ` Radu Moisan
2012-07-26 9:51 ` Koen Kooi
2012-07-26 10:23 ` Burton, Ross
2012-07-26 10:36 ` Radu Moisan
2012-07-26 10:31 ` Radu Moisan
2012-07-26 10:55 ` Radu Moisan
2012-07-26 11:27 ` Burton, Ross
2012-07-26 11:55 ` Koen Kooi
2012-07-26 12:00 ` Burton, Ross
2012-07-26 12:29 ` Koen Kooi
2012-07-26 12:32 ` Paul Eggleton
2012-07-26 12:38 ` Koen Kooi
2012-07-26 12:56 ` Paul Eggleton
2012-07-26 13:06 ` Radu Moisan
2012-07-26 13:07 ` Koen Kooi
2012-07-26 13:12 ` Paul Eggleton
2012-07-26 13:21 ` Koen Kooi
2012-07-26 12:36 ` Radu Moisan [this message]
2012-07-26 12:51 ` Koen Kooi
2012-07-26 12:59 ` Radu Moisan
2012-07-26 13:08 ` Enrico Scholz
2012-07-26 13:24 ` Radu Moisan
2012-07-26 14:32 ` Enrico Scholz
2012-07-26 21:14 ` Burton, Ross
2012-07-26 13:17 ` Enrico Scholz
2012-07-26 21:12 ` Burton, Ross
2012-07-27 6:10 ` Radu Moisan
2012-07-27 6:15 ` Radu Moisan
2012-07-27 10:02 ` Burton, Ross
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=501139E2.1020003@intel.com \
--to=radu.moisan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox