exec enlightenment instead of enlightenment_start 85/35785/1 accepted/tizen/common/20150225.131130 accepted/tizen/mobile/20150226.013412 accepted/tizen/tv/20150226.011154 accepted/tizen/wearable/20150226.012708 submit/tizen/20150225.044102
authorBoram Park <boram1288.park@samsung.com>
Tue, 24 Feb 2015 12:45:12 +0000 (21:45 +0900)
committerBoram Park <boram1288.park@samsung.com>
Tue, 24 Feb 2015 12:45:12 +0000 (21:45 +0900)
commit77d3d4d6513294b4ff8eaaacb466f59c840d2790
tree5f5e082ad7139808fa1fee0e51aee4f590034feb
parent9e3b11e1d29c2da6d045bef3b43f0c1ce9625237
exec enlightenment instead of enlightenment_start

    Refer to below commit of mainstream. enlightenment_start can't
    be used to start enlightenment in systemd.

    -------------------------------------------------------
    commit 6f955263fa76649682066adc82f12d4249d9c3d0
    Author: Cedric BAIL <cedric.bail@samsung.com>
    Commit: Cedric BAIL <cedric.bail@samsung.com>

    enlightenment: do not propagate the systemd socket to E17.

    In a proper systemd user session setup, enlightenment_start will be
    gone. That is still not doable today and as I plan to roll more feature
    in EFL regarding systemd, we need to prevent enlightenment to believe
    it is the process started by systemd.

Change-Id: I8cfcef9abf9318da3babd96c7f9191796fe0fabb
packaging/enlightenment.service