All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chong Lu <Chong.Lu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2 1/1] gconf: fix multilib conflict - org.gnome.GConf.service
Date: Mon, 20 Oct 2014 17:19:33 +0800	[thread overview]
Message-ID: <5444D3A5.7060208@windriver.com> (raw)
In-Reply-To: <CAJTo0LboKNAOi7_tx31+m2KOxF_HEKEGePU2wnHXSzGpoeGTgA@mail.gmail.com>


On 10/15/2014 06:42 PM, Burton, Ross wrote:
> On 15 October 2014 03:54, Chong Lu <Chong.Lu@windriver.com> wrote:
>> 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
>>
>> Split org.gnome.GConf.service to ${PN}-service, the conflict was fixed.
> Why are both ML variants of gconf being installed?    Presumably for
> libgconf, which needs to have ML variants and is packaged into $PN.
> $PN also contains the binaries and data files, which are not

Hi Ross,

The data file is different between bit-32 and bit-64 environment.

Best Regards
Chong

> ML-specific and can only be installed once.
>
> So, gconf should split the daemon/binaries from the libraries.  I
> suggested this back in July as it seems the logical answer, instead of
> splitting the daemon binary and the service file that defines where
> the binary is.
>
> Ross
>
>



  parent reply	other threads:[~2014-10-20  9:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15  2:54 [PATCH V2 0/1] gconf: fix multilib conflict - org.gnome.GConf.service Chong Lu
2014-10-15  2:54 ` [PATCH V2 1/1] " Chong Lu
2014-10-15 10:42   ` Burton, Ross
2014-10-16  2:40     ` Chong Lu
2014-10-20  9:19     ` Chong Lu [this message]
2014-10-20 12:31       ` Burton, Ross
2014-10-22  6:19         ` Chong Lu
2014-10-20 10:21     ` Koen Kooi

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=5444D3A5.7060208@windriver.com \
    --to=chong.lu@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 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.