busybox: don't remove S01logging when CONFIG_SYSLOGD is disabled
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Wed, 10 Jan 2018 22:03:59 +0000 (23:03 +0100)
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Wed, 10 Jan 2018 22:03:59 +0000 (23:03 +0100)
commit84e835ea9261b3e844f1a18489dd89253e3eb839
tree62edf39aa292943b4db8f5c9c7c6c7238116ed4e
parent28d5ca9c96f5144e86fac7ec6485fa5634cd6e97
busybox: don't remove S01logging when CONFIG_SYSLOGD is disabled

The current busybox.mk explicitly removes S01logging if CONFIG_SYSLOGD
is disabled in the Busybox configuration. However:

 - This causes the removal of the S01logging script potentially
   installed by another package (currently syslog-ng, rsyslog and
   sysklogd can all install a S01logging script).

 - We generally don't try to clean-up stuff that we may have installed
   in a previous make invocation and that is no longer needed
   following a configuration change.

Fixes bug #10176

Reported-by: Karl Krach <mail@kkrach.de>
Fix-provided-by: Karl Krach <mail@kkrach.de>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
package/busybox/busybox.mk