Hi,
Thanks for the tips. I will do as suggested.
I have another question. Will we need dbus smack patches? I see them
used in Automotive Message Broker configuration file
(/etc/dbus-1/system.d/manifest.automotive-message-broker.conf), but will
it stay this way? Porting these patches shouldn't be a problem, but if
they are not required it's better to drop them.
I also see that smack-specific D-Bus daemon method
"GetConnectionSmackContext" is used in several packages (cynara,
gsignond, polkit) so I believe it should be picked, at least for now.
However, in the future these packages should be changed so they use
"GetConnectionCredentials" method which is provided by the upstream D-Bus.
Best regards,
Jacek
On 10/10/2014 02:39 PM, Dominig ar Foll (Intel OTC) wrote:
Hello,
using a development version is not a great idea, but waiting until
1.10 might not be possible.
We will release Tizen Comon Q3 and Tizen IVI 14.3 before the end of
the month.
So updating just after those two releases would be ideal.
Please sync with Stéphane to get early test done on his private OBS
and in the Dev branch of Tizen Common in advance of phase.
Regards
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
Le 09/10/2014 23:56, Thiago Macieira a écrit :
On Thursday 09 October 2014 12:47:54 Jacek Bukarewicz wrote:
What do you think about potential upgrade? Do you have any
objections to
do it now? I believe best candidate would be 1.8.8. On 1 October
version
1.9.0 has been released, but it might be too early to use this one.
1.9.0 is a development version. We shouldn't switch to it. Instead,
we'd wait
until 1.10.0.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
--
Jacek Bukarewicz
Samsung R&D Institute Poland
Samsung Electronics
[email protected]
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
