Openembedded Core Discussions
 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: Wed, 22 Oct 2014 14:19:36 +0800	[thread overview]
Message-ID: <54474C78.5030509@windriver.com> (raw)
In-Reply-To: <CAJTo0La=Q6Wx8dTBP6mc6A3=b-oXejiAX94dMtgon5aohA1GQg@mail.gmail.com>


On 10/20/2014 08:31 PM, Burton, Ross wrote:
> On 20 October 2014 10:19, Chong Lu <Chong.Lu@windriver.com> wrote:
>> The data file is different between bit-32 and bit-64 environment.
> And the data file is specific to the daemon, and you only want that
> installed once.  Two gconf daemons will attempt to write the same data
> file, resulting in corruption.
>
> What I meant is this:
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=ross/gconf&id=fac86eb3f86618f109e3797422aae53d9c8d3b30.
> Package the client-side libraries into a separate package, so you can
> have gconfd, libgconf, and lib32-libgconf installed at once.  Both
> client libraries will talk over DBus to the single gconfd binary.
>
> (untested, and needs upgrade path dependencies added)
>
> Ross

Hi Ross,

Thanks for your suggestion, I will send a V3.

Best Regards
Chong

>
>



  reply	other threads:[~2014-10-22  6: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
2014-10-20 12:31       ` Burton, Ross
2014-10-22  6:19         ` Chong Lu [this message]
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=54474C78.5030509@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox