On Thu, 2014-12-18 at 10:25 +0100, Corentin Lecouvey wrote: > Hi Zheng Wu, > > Yeah I saw that, unfortunately I do not have time to take a look at NTB > 0.3 release due to Tizen releases. > > I'm afraid that we won't be able to merge NTB into Tizen before Tizen > IVI M14.4 and Tizen Common Q4 releases. > > From my point of view, NTB is *not* ready to be merged on Tizen right now. > > There are some Tizen configurations that need to be added in order to be > merged : > - Smack labels are not correct and so NTB daemon can not create bt user > privilege file (https://bugs.tizen.org/jira/browse/TC-1981) > - Dbus activation doesn't work on Tizen Common since it required missing > 'app' user. > We would like to get a specific user for running bluetooth components on > Tizen (https://bugs.tizen.org/jira/browse/TC-1972) > > I've not finished this job, but it has to be done before merging...
I've also said it in https://bugs.tizen.org/jira/browse/TC-1972 but it is worth repeating here: NTB cannot be integrated like that unless it also supports PBAB transfers initiated by users. We have features in Tizen IVI depending on that (Modello/phoned, SyncEvolution). I asked about the PBAP API earlier [1] but got no response. As has become clear in TC-1972, PBAP will no longer work once TC-1972 is implemented and also isn't planned to be supported. I find that unacceptable and therefore have to put in a veto. I'll disagree and commit, of course, when the steering committee for Tizen decides otherwise. [1] http://permalink.gmane.org/gmane.comp.handhelds.tizen.devel/4677 -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
