> Op 15 okt. 2014, om 12:42 heeft Burton, Ross <ross.bur...@intel.com> het
> volgende geschreven:
>
> On 15 October 2014 03:54, Chong Lu <chong...@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
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
