Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ming Liu <ming.liu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gconf: fix multilib conflict - org.gnome.GConf.service
Date: Mon, 7 Jul 2014 18:07:25 +0800	[thread overview]
Message-ID: <53BA715D.6010901@windriver.com> (raw)
In-Reply-To: <CAJTo0LbLcADdC0qC7cYNDWoZOjvj_BXg42-K4siPE518MykU2Q@mail.gmail.com>

On 07/07/2014 05:40 PM, Burton, Ross wrote:
> On 5 July 2014 07:06, Ming Liu <ming.liu@windriver.com> wrote:
>> 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
> Your patch doesn't move the file that is conflicting so it won't help...
>
> As you'll only ever install a single instance of the binaries, the
> correct fix would be to split the ML-appropriate libraries into a
> libgconf, but leave the DBus service and tools in the main package.
> Then multilib images can install lib32gconf, lib64gconf, and gconf.
Hi, Ross:

I got your point, but my patch was not tring to address the conflict of 
binaries or libraries, that kind of conflicts would not cause build 
error, as you pointed out, only ever a single instance be installed at 
one time. It's actually tring to fix a conflict of conf file, if the 
gconfd-2 is put into libexec directory, we have to keep a path like 
/usr/lib64/gconf/gconfd-2(or /usr/lib/gconf/gconfd-2 in lib32 case) 
referring it in /usr/share/dbus-1/services/org.gnome.GConf.service which 
will cause the conflict.

the best,
thank you
>
> Ross
>
>



  reply	other threads:[~2014-07-07 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05  6:06 [PATCH] gconf: fix multilib conflict - org.gnome.GConf.service Ming Liu
2014-07-07  9:40 ` Burton, Ross
2014-07-07 10:07   ` Ming Liu [this message]
2014-07-07 10:38     ` Burton, Ross
2014-07-08  8:07       ` Ming Liu

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=53BA715D.6010901@windriver.com \
    --to=ming.liu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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