W dniu 04.12.2014 o 21:44 Dominig ar Foll (Intel OTC)
<[email protected]> pisze:
Le 04/12/2014 19:37, Thiago Macieira a écrit :
Are we still going to update systemd in the next month or so? We're
REALLY
close to the Common 3.0 release now. Shouldn't this feature go to Tizen
3.1 or
so?
Likely not, 2.16 is the version used by Yocto 1.7, so we have no
motivation to change.
Yes, we know that. We were preparing update to v217, but settled on v216
because of Yocto. I think that Tizen development will be really painful if
only motivation for updates are Yocto versions and not (desired) features
provided by new versions.
Anyway we have plans to provide kdbus-enabled Tizen Common images, which
would be beneficial not only for kdbus on Tizen integration, but also for
developers who are planning to use kdbus in the future. That said, we are
aware of fact, that kdbus is not stable and we don't want to push it to
Tizen 3.0.
Back to memfd: it is independent from kdbus, shipped since 3.17 in
upstream kernel. It is used by kdbus, but there's no contradictions to use
memfd+sealing in other software (which can be independent from (k)dbus).
Also I'll try to get memfd to 3.14 LTSI. But even if it won't make there
we'll have to backport it anyway if we want to have kdbus. So memfd will
have to be backported sooner or later.
regards,
--
Maciej Wereski
Samsung R&D Institute Poland
Samsung Electronics
[email protected]
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
