From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 10 Sep 2019 19:38:03 +0200 Subject: [Buildroot] [PATCH 2/2] eventlog: remove package In-Reply-To: <20190909095432.3935-2-judge.packham@gmail.com> References: <20190909095432.3935-1-judge.packham@gmail.com> <20190909095432.3935-2-judge.packham@gmail.com> Message-ID: <20190910193803.461857fa@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Mon, 9 Sep 2019 21:54:32 +1200 Chris Packham wrote: > Since syslog-ng 3.11.1 eventlog has been bundled with the sources. > Remove the separate package. > > Signed-off-by: Chris Packham > --- > DEVELOPERS | 1 - > package/Config.in | 1 - > package/eventlog/Config.in | 8 -------- > package/eventlog/eventlog.hash | 2 -- > package/eventlog/eventlog.mk | 15 --------------- > package/syslog-ng/syslog-ng.mk | 2 +- > 6 files changed, 1 insertion(+), 28 deletions(-) > delete mode 100644 package/eventlog/Config.in > delete mode 100644 package/eventlog/eventlog.hash > delete mode 100644 package/eventlog/eventlog.mk The question is whether we need Config.in.legacy handling for the removal of this package/option. Since it seems like the only user of eventlog was syslog-ng, then supposedly anyone having eventlog enabled also has syslog-ng enabled. If that's the case, then we probably can do without any Config.in.legacy handling, because silently dropping the BR2_PACKAGE_EVENTLOG=y when Buildroot gets updated is the right thing. Chris, Arnout, any opinion on this ? Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com