projects / platform / core / security / pubkey-pinning.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8b5c184) | patch
Split rpm of popup ui service 39/114839/3 accepted/tizen_common accepted/tizen_ivi accepted/tizen_mobile accepted/tizen_tv accepted/tizen_wearable accepted/tizen/common/20170222.124426 accepted/tizen/ivi/20170222.094722 accepted/tizen/mobile/20170222.094633 accepted/tizen/tv/20170222.094649 accepted/tizen/unified/20170309.033733 accepted/tizen/wearable/20170222.094705 submit/tizen/20170222.022045 submit/tizen_unified/20170308.100409
authorKyungwook Tak <k.tak@samsung.com>
Wed, 15 Feb 2017 07:52:10 +0000 (16:52 +0900)
committerKyungwook Tak <k.tak@samsung.com>
Thu, 16 Feb 2017 06:59:31 +0000 (15:59 +0900)
commita7eca811f384b4125f81c96e030efb7dc1ff7852
tree86973d88460a11c9b9e333c70629c3a6ddfb8e4ftree | snapshot
parent8b5c184adca12e32f3fc82008e07affc31888b28commit | diff
Split rpm of popup ui service

There could be profile which doesn't includes UI framework. For those
profile, ui popup module can be excluded easily and it's determined by
socket file existance (IO error when socket send) and response will be
always 'ALLOW'.

For profile who supports UI, ui rpm should be included explicitly
(because the dependency to ui rpm isn't explicitly defined)

Change-Id: I67576a3f46b1d4c6ed36481cb08594d8ecab35eb
Signed-off-by: Kyungwook Tak <k.tak@samsung.com>
packaging/pubkey-pinning.spec diff | blob | history
src/common/ui/popup_runner.cpp diff | blob | history
Domain: Security / Authentication;