* Re: [PATCH V2 1/1] gconf: fix multilib conflict - org.gnome.GConf.service
2014-10-15 10:42 ` Burton, Ross
@ 2014-10-16 2:40 ` Chong Lu
2014-10-20 9:19 ` Chong Lu
2014-10-20 10:21 ` Koen Kooi
2 siblings, 0 replies; 8+ messages in thread
From: Chong Lu @ 2014-10-16 2:40 UTC (permalink / raw)
To: Burton, Ross; +Cc: OE-core
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
> 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
Hi Ross,
Sorry, I don't understand your solution.
In org.gnome.GConf.service.in file, it has following line:
Exec=@libexecdir@/gconfd-2
And then, in Makefile.am file:
org.gnome.GConf.service: $(srcdir)/org.gnome.GConf.service.in
sed -e 's,[@]libexecdir[@],$(libexecdir),g' \
<$(srcdir)/org.gnome.GConf.service.in
>org.gnome.GConf.service
In 32bit and 64bit environment, the path of gconfd-2 is different.
So, if we want to install both gconf and lib32-gconf in a image, the
error will get as above.
In fact, I want to resolve this confliction. Do you have any suggestions?
Best Regards
Chong
>
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH V2 1/1] gconf: fix multilib conflict - org.gnome.GConf.service
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-20 10:21 ` Koen Kooi
2 siblings, 1 reply; 8+ messages in thread
From: Chong Lu @ 2014-10-20 9:19 UTC (permalink / raw)
To: Burton, Ross; +Cc: OE-core
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
>
>
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH V2 1/1] gconf: fix multilib conflict - org.gnome.GConf.service
2014-10-20 9:19 ` Chong Lu
@ 2014-10-20 12:31 ` Burton, Ross
2014-10-22 6:19 ` Chong Lu
0 siblings, 1 reply; 8+ messages in thread
From: Burton, Ross @ 2014-10-20 12:31 UTC (permalink / raw)
To: Chong Lu; +Cc: OE-core
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH V2 1/1] gconf: fix multilib conflict - org.gnome.GConf.service
2014-10-20 12:31 ` Burton, Ross
@ 2014-10-22 6:19 ` Chong Lu
0 siblings, 0 replies; 8+ messages in thread
From: Chong Lu @ 2014-10-22 6:19 UTC (permalink / raw)
To: Burton, Ross; +Cc: OE-core
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
>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH V2 1/1] gconf: fix multilib conflict - org.gnome.GConf.service
2014-10-15 10:42 ` Burton, Ross
2014-10-16 2:40 ` Chong Lu
2014-10-20 9:19 ` Chong Lu
@ 2014-10-20 10:21 ` Koen Kooi
2 siblings, 0 replies; 8+ messages in thread
From: Koen Kooi @ 2014-10-20 10:21 UTC (permalink / raw)
To: Burton, Ross; +Cc: OE-core
> Op 15 okt. 2014, om 12:42 heeft Burton, Ross <ross.burton@intel.com> het volgende geschreven:
>
> 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
> 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.
Keep in mind that both solutions mentioned above will make it virtually impossible to keep a working upgrade path.
regards,
Koen
^ permalink raw reply [flat|nested] 8+ messages in thread