Dear Philippe,
Hello, I'm Jiyoung Yun, in charge of sysman and other system modules.
Sorry for late response.
Rigarding PTREL-643 issue:
Last thursday, below patch that includes VCONFKEY_PM_LCDOFF_SOURCE was merged.
https://review.tizen.org/gerrit/#/c/14900/
I had already known system-server package occurs build break issue for missing some vconf key.
So I was searching for owner of vconf key module in recent weeks,
Finally i found the maintainer of vconf key, then the vconf key patch was merged in last thursday.
Regarding PTREL-493 issue:
Could you give me more information which vconf key you need ?
And did you build your package recently (after last thursday) ?
Thank you.
------- Original Message -------
Sender : Philippe Coval<[email protected]>
Date : 2014-02-27 23:57 (GMT+09:00)
Title : [Dev] Possible Workflow issues caused by unsync availability of sources
Hi,
It seems that some sources are missing on tizen's git,
I mean that some packages are outdated
(some changes may exist somewhere but haven't been pushed )
while others updated packages are depending on
those unpublished codes and then remain unbuildable ...
The good thing is that they aren't submitted/accepted in repos
but are present in current git's HEAD.
For instance system-server is using some unavailable vconf keys
(VCONFKEY_PM_LCDOFF_SOURCE)
probably provided by some power package
https://bugs.tizen.org/jira/browse/PTREL-643
At the same time I noticed that upstream's efl-1.8 add some tizen features
that are requiring some unavailable code (ie sysman news vconf keys also)
https://bugs.tizen.org/jira/browse/PTREL-493
I can understand those codes are not released for good reasons,
but it would help to have access to them,
maybe in sandboxes in the first time (ie sandbox/$maintainer/devel) ?
to avoid working in opposite directions and in the end exhausting
ourselves :)
Until missing code is released the alternative
is to temporary disable using it to unblock and use current git tree
or branch from latest stable state
but I feel this is really unproductive and would be nice to avoid.
Tell me if I am wrong but this is looks like a workflow pitfall,
since last year some packages were unsync on tizen-2.2
I guess this is the same with ongoing developments...
Maybe it would help to list all those unsync availability troubles..
but It at this time I would encourage to use bugtracker
and make sure requests will reach the right person (active maintainer?)
or can you suggest someone else ?
Hope this help to improve our cooperation model ...
Regards
--
mailto:[email protected] -- gpg:0x467094BC
xmpp:[email protected]
https://dockr.eurogiciel.fr/blogs/embedded/author/pcl/
.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
|
|
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
