From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Cc: Clemens Gruber <clemens.gruber@pqgruber.com>
Subject: [ptxdist] [PATCH] lldpd: bump version and add missing dependencies
Date: Sat, 6 Feb 2016 16:06:17 +0100 [thread overview]
Message-ID: <1454771177-2588-1-git-send-email-clemens.gruber@pqgruber.com> (raw)
Bump version to 0.9.0, adjust the kernel version for the oldies flag and
add the missing readline and libbsd dependencies, which are not
optional.
This was probably missed, because both libraries were already selected
on many systems.
Signed-off-by: Clemens Gruber <clemens.gruber@pqgruber.com>
---
rules/lldpd.in | 4 +++-
rules/lldpd.make | 4 ++--
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/rules/lldpd.in b/rules/lldpd.in
index e7d3f51..0f6d475 100644
--- a/rules/lldpd.in
+++ b/rules/lldpd.in
@@ -4,7 +4,9 @@ menuconfig LLDPD
tristate
prompt "lldpd "
select INITMETHOD
+ select LIBBSD
select LIBEVENT
+ select READLINE
select NET_SNMP if LLDPD_SNMP
select NET_SNMP_MIB_MODULES_AGENTX if LLDPD_SNMP
select JSON_C if LLDPD_JSON
@@ -74,7 +76,7 @@ config LLDPD_CUSTOM_TLV
config LLDPD_OLDIES
bool
- prompt "Enable compatibility with Linux kernel older than 2.6.32"
+ prompt "Enable compatibility with Linux kernel older than 2.6.39"
config LLDPD_SNMP
bool
diff --git a/rules/lldpd.make b/rules/lldpd.make
index a798ca5..a6e5862 100644
--- a/rules/lldpd.make
+++ b/rules/lldpd.make
@@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_LLDPD) += lldpd
#
# Paths and names
#
-LLDPD_VERSION := 0.7.19
-LLDPD_MD5 := 4e924420e00ccd5dc289506f43221820
+LLDPD_VERSION := 0.9.0
+LLDPD_MD5 := ed0226129b0c90b3a45c273fe1aba8de
LLDPD := lldpd-$(LLDPD_VERSION)
LLDPD_SUFFIX := tar.gz
LLDPD_URL := http://media.luffy.cx/files/lldpd//$(LLDPD).$(LLDPD_SUFFIX)
--
2.7.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2016-02-06 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 15:06 Clemens Gruber [this message]
2016-02-11 11:30 ` Michael Olbrich
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=1454771177-2588-1-git-send-email-clemens.gruber@pqgruber.com \
--to=clemens.gruber@pqgruber.com \
--cc=ptxdist@pengutronix.de \
/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