lpppd: new package
PATCH 1/1 lpppd: new package
From: Stefan Nickl <[email protected]>
After the official github repository for PPP has not seen any activity for a long time, I've created a fork that tries to do some modernization and shed some legacy. For more info, please see https://github.com/snickl/lpppd
It is inteded as a drop-in replacement for the original PPP, therefore I've marked it as conflicting with the existing pppd package.
--- package/Config.in | 1 + package/lpppd/Config.in | 34 ++++++++++++++++++++++++++++++++++ package/lpppd/lpppd.hash | 2 ++ package/lpppd/lpppd.mk | 31 +++++++++++++++++++++++++++++++ 4 files changed, 68 insertions(+) create mode 100644 package/lpppd/Config.in create mode 100644 package/lpppd/lpppd.hash create mode 100644 package/lpppd/lpppd.mk
package/Config.in +1 -0
@@ -1527,6 +1527,7 @@ menu "Networking applications" source "package/linphone/Config.in" source "package/linux-zigbee/Config.in" source "package/lldpd/Config.in" + source "package/lpppd/Config.in" source "package/lrzsz/Config.in" source "package/macchanger/Config.in" source "package/memcached/Config.in"
package/lpppd/Config.in new file +34 -0
@@ -0,0 +1,34 @@ +config BR2_PACKAGE_LPPPD + bool "lpppd" + depends on !BR2_STATIC_LIBS + depends on !BR2_PACKAGE_PPPD + depends on BR2_USE_MMU + help + A fork of the Point-to-point protocol daemon + for Linux systems. + + https://github.com/snickl/lpppd + +if BR2_PACKAGE_LPPPD + +config BR2_PACKAGE_LPPPD_FILTER + select BR2_PACKAGE_LIBPCAP + bool "filtering" + help + Packet filtering abilities for lpppd. If enabled, + the lpppd active-filter and pass-filter options + are available. + +config BR2_PACKAGE_LPPPD_MULTILINK + bool "multilink" + help + Enable multilink + +endif + +comment "lpppd conflicts with pppd" + depends on BR2_PACKAGE_PPPD + +comment "lpppd needs a toolchain w/ dynamic library" + depends on BR2_STATIC_LIBS + depends on BR2_USE_MMU
package/lpppd/lpppd.hash new file +2 -0
@@ -0,0 +1,2 @@ +# Locally computed: +sha256 d171cccd680abfd11975c9e58b0804b5677a272b126088fa338bae5f606c10c6 lpppd-v1.tar.gz
package/lpppd/lpppd.mk new file +31 -0
@@ -0,0 +1,31 @@ +################################################################################ +# +# lpppd +# +################################################################################ + +LPPPD_VERSION = v1 +LPPPD_SITE = $(call github,snickl,lpppd,$(LPPPD_VERSION)) +LPPPD_LICENSE = LGPLv2+, LGPL, BSD-4c, BSD-3c, GPLv2+ +LPPPD_LICENSE_FILES = \ + pppd/tdb.c pppd/plugins/pppoatm/COPYING \ + pppdump/bsd-comp.c pppd/ccp.c pppd/plugins/passprompt.c + +LPPPD_CONF_OPTS = -DOPTION_LPPPD_INET6=ON + +ifeq ($(BR2_PACKAGE_LPPPD_FILTER),y) +LPPPD_DEPENDENCIES += libpcap +LPPPD_CONF_OPTS += -DOPTION_LPPPD_PPPD_FILTER=ON +endif + +ifeq ($(BR2_PACKAGE_LPPPD_MULTILINK),y) +LPPPD_CONF_OPTS += -DOPTION_LPPPD_PPPD_MULTILINK=ON +endif + +define LPPPD_INSTALL_TARGET_CMDS + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) DESTDIR="$(TARGET_DIR)" install + $(INSTALL) -D -m 0755 $(LPPPD_DIR)/scripts/pon $(TARGET_DIR)/usr/bin/pon + $(INSTALL) -D -m 0755 $(LPPPD_DIR)/scripts/poff $(TARGET_DIR)/usr/bin/poff +endef + +$(eval $(cmake-package))
Signature · 1 line
2.9.3
PATCH 1/1 lpppd: new package
Hello Stefan,
Quoted 7 lines · stefan.nickl at gmail.com
From: Stefan Nickl <[email protected]>
After the official github repository for PPP has not seen any activity for a long time, I've created a fork that tries to do some modernization and shed some legacy. For more info, please see https://github.com/snickl/lpppd
Quoted 5 lines
It is inteded as a drop-in replacement for the original PPP, therefore I've marked it as conflicting with the existing pppd package.
Signed-off-by Stefan Nickl <[email protected]>
I do appreciate your interest in making the pppd development active again. However, at this point, I don't see what is the benefit of using lpppd over pppd, and having two separate packages is a bit annoying. Therefore, I would prefer to wait for lpppd to gain some traction before packaging it in Buildroot.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 1/1 lpppd: new package
Stefan, All,
On 2017-04-01 18:40 +0200, Thomas Petazzoni spake thusly:
Quoted 12 lines · stefan.nickl at gmail.com
Quoted 11 lines
From: Stefan Nickl <[email protected]>
After the official github repository for PPP has not seen any activity for a long time, I've created a fork that tries to do some modernization and shed some legacy. For more info, please see https://github.com/snickl/lpppd
It is inteded as a drop-in replacement for the original PPP, therefore I've marked it as conflicting with the existing pppd package.
Quoted 7 lines
Quoted 1 line
Signed-off-by Stefan Nickl <[email protected]>I do appreciate your interest in making the pppd development active again. However, at this point, I don't see what is the benefit of using lpppd over pppd, and having two separate packages is a bit annoying. Therefore, I would prefer to wait for lpppd to gain some traction before packaging it in Buildroot.
I kind of agree with Thomas here.
lpppd is a new fork of a well-established project, so it will have to offer enough of an edge before it can displace pppd.
However, I agree with you that there is no activity in upstream pppd. Maybe you could talk with upstream to adopt the package instead of forking?
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 lpppd: new package
Thomas, Yann,
Quoted 23 lines · Yann E. MORIN
Stefan, All,
On 2017-04-01 18:40 +0200, Thomas Petazzoni spake thusly:
Quoted 12 lines · stefan.nickl at gmail.com
Quoted 11 lines
From: Stefan Nickl <[email protected]>
After the official github repository for PPP has not seen any activity for a long time, I've created a fork that tries to do some modernization and shed some legacy. For more info, please see https://github.com/snickl/lpppd
It is inteded as a drop-in replacement for the original PPP, therefore I've marked it as conflicting with the existing pppd package.
Quoted 7 lines
Quoted 1 line
Signed-off-by Stefan Nickl <[email protected]>I do appreciate your interest in making the pppd development active again. However, at this point, I don't see what is the benefit of using lpppd over pppd, and having two separate packages is a bit annoying. Therefore, I would prefer to wait for lpppd to gain some traction before packaging it in Buildroot.
Quoted 8 lines
I kind of agree with Thomas here.
lpppd is a new fork of a well-established project, so it will have to offer enough of an edge before it can displace pppd.
However, I agree with you that there is no activity in upstream pppd. Maybe you could talk with upstream to adopt the package instead of forking?
The trouble with ppp (as in "Paul's PPP package") is that it carries a lot of baggage through its wide range of support for different systems and legacy protocols.
Now I'm one guy interested only in the embedded Linux use case, and the approach with lpppd is to focus on that, shedding stuff like Solaris and IPX support in the hope that what remains will be maintainable and testable.
Interestingly enough, Paul Mackerras showed up on the github project half a month ago and accepted some pull requests, but has not followed up on any of the comments I made there since, so I guess the upstream project will continue to remain in this sort of limbo state.
I'm also pretty sure there are other people out there that still depend on much of this legacy support, so a fork with much narrower goals seems like the only way for moving forward the embedded Linux case, and getting e.g. support for musl-libc in.
I can fully understand that you'd rather see the fork getting traction outside of Buildroot first, but I'm submitting lpppd in an attempt to overcome that chicken-and-egg dilemma from the other side, by getting the fork some visibility towards a like-minded audience and see if it sticks.
So the decision is up to you guys; I'd rather you not accept it for now than setting expectations towards myself that I might not be able to keep.
Signature · 1 line
Stefan