From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] eventlog: remove package
Date: Tue, 10 Sep 2019 19:38:03 +0200 [thread overview]
Message-ID: <20190910193803.461857fa@windsurf> (raw)
In-Reply-To: <20190909095432.3935-2-judge.packham@gmail.com>
On Mon, 9 Sep 2019 21:54:32 +1200
Chris Packham <judge.packham@gmail.com> wrote:
> Since syslog-ng 3.11.1 eventlog has been bundled with the sources.
> Remove the separate package.
>
> Signed-off-by: Chris Packham <judge.packham@gmail.com>
> ---
> 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
next prev parent reply other threads:[~2019-09-10 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 9:54 [Buildroot] [PATCH 1/2] syslog-ng: update version in config file Chris Packham
2019-09-09 9:54 ` [Buildroot] [PATCH 2/2] eventlog: remove package Chris Packham
2019-09-10 17:38 ` Thomas Petazzoni [this message]
2019-09-14 17:36 ` Arnout Vandecappelle
2019-09-15 13:38 ` Thomas Petazzoni
2019-09-10 0:09 ` [Buildroot] [PATCH 1/2] syslog-ng: update version in config file Carlos Santos
2019-09-10 17:35 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190910193803.461857fa@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox