From: Anders Darander <anders@chargestorm.se>
To: Chong Lu <Chong.Lu@windriver.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V3 1/1] gconf: fix multilib conflict - org.gnome.GConf.service
Date: Fri, 24 Oct 2014 09:01:47 +0200 [thread overview]
Message-ID: <20141024070147.GA16284@ad.chargestorm.se> (raw)
In-Reply-To: <5449EEC4.4070303@windriver.com>
* Chong Lu <Chong.Lu@windriver.com> [141024 08:17]:
> On 10/24/2014 02:10 PM, Koen Kooi wrote:
> >> Op 22 okt. 2014, om 09:09 heeft Chong Lu <Chong.Lu@windriver.com> het volgende geschreven:
> >> The gconfd-2 will be called in org.gnome.GConf.service file and the path of
> >> gconfd-2 is ${libexecdir}, this will get following error when multilib exported
> >> in the sdk:
> >> error: file /usr/share/dbus-1/services/org.gnome.GConf.service from install
> >> of gconf-3.2.6-r0.0.lib32_x86 conflicts with file from package
> >> gconf-3.2.6-r0.0.x86_64
> >> Move org.gnome.GConf.service to ${libdir}, then the conflict was fixed.
> > And I suspect its dbus service won't work anymore after moving the files. How have you tested this change?
> I just focus on the conflicts, not to test dbus service.
> Or do you have any suggestion to fix this conflicts?
Well, if you move a file to a new location, everyone assumes that you
have verified that the file still will be found by the application that
needs it. Basically, that's what Koen's question was about. Have you
made any run-time tests, to verify that your patch doesn't break
anything?
Besides, there was the other remark whether or not it makes sense to
have multiple versions of gconf installed...
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
prev parent reply other threads:[~2014-10-24 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 7:09 [PATCH V3 0/1] gconf: fix multilib conflict - org.gnome.GConf.service Chong Lu
2014-10-22 7:09 ` [PATCH V3 1/1] " Chong Lu
2014-10-22 10:07 ` Burton, Ross
2014-10-22 10:58 ` Mark Hatle
2014-10-22 11:04 ` Burton, Ross
2014-10-24 2:26 ` Chong Lu
2014-10-26 20:58 ` Burton, Ross
2014-10-24 6:10 ` Koen Kooi
2014-10-24 6:16 ` Chong Lu
2014-10-24 7:01 ` Anders Darander [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=20141024070147.GA16284@ad.chargestorm.se \
--to=anders@chargestorm.se \
--cc=Chong.Lu@windriver.com \
--cc=koen@dominion.thruhere.net \
--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