Revert "logger: detect proper apps/events buffer path" 79/181379/1
authorMichal Bloch <m.bloch@samsung.com>
Tue, 12 Jun 2018 15:07:38 +0000 (17:07 +0200)
committerMichal Bloch <m.bloch@samsung.com>
Tue, 12 Jun 2018 15:21:03 +0000 (17:21 +0200)
commit39c12c4aa1010b06044566c53ffbf40342b1a023
treeab7fd928f826e70f65d669f7bacd58eaf061796d
parent99013cc83a15250a6acda25f637abe9fea898266
Revert "logger: detect proper apps/events buffer path"

This reverts commit f4fe42b5dc8dcff4572353675c1bc52a62d7d939.

The post-install script works correctly as long as the package
is installed on the target directly. However, it won't work if
it arrives on the target by being included in an image, due to
the post-install script having been ran on a different system,
the one where the image had been built and not the target one.

There isn't a strict regression because the end result is that
the image sometimes contains the other path (which means there
are still some devices that will work and some that won't), so
there might still be value to keeping the change as a reminder
of the underlying problem of Android log device availablility.

Change-Id: Id71b5a66d3115fdac876ad06c51aed607a31b452
Signed-off-by: Michal Bloch <m.bloch@samsung.com>
Makefile.am
configs/25-logger.conf
configs/26-logger-apps.conf.inactive [deleted file]
configs/26-logger-events.conf.inactive [deleted file]
packaging/dlog.spec
src/shared/logconfig.c