Thomas Petazzoni 84e835ea92 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>		2018-01-10 23:03:59 +01:00
..
0001-networking-libiproute-use-linux-if_packet.h-instead-.patch
0002-Makefile.flags-strip-non-l-arguments-returned-by-pkg.patch
0003-Makefile-include-per-arch-Makefile-before-Makefile.f.patch
0004-arch-sparc-sparc64-Makefile-define-ARCH_FPIC.patch
0005-httpd-fix-handling-of-range-requests.patch
busybox-minimal.config
busybox.config
busybox.hash	package/busybox: add license hash	2017-11-05 17:45:05 +01:00
busybox.mk	busybox: don't remove S01logging when CONFIG_SYSLOGD is disabled	2018-01-10 23:03:59 +01:00
Config.in
inittab
mdev.conf
S01logging
S10mdev
S15watchdog
S50telnet
udhcpc.script