2019-01-27 13:07:52 +01:00
|
|
|
include $(TOPDIR)/rules.mk
|
|
|
|
|
|
|
|
|
|
PKG_NAME:=464xlat
|
package: drop PKG_VERSION for purely local packages
In the package guidelines, PKG_VERSION is supposed to be used as
"The upstream version number that we're downloading", while
PKG_RELEASE is referred to as "The version of this package Makefile".
Thus, the variables in a strict interpretation provide a clear
distinction between "their" (upstream) version in PKG_VERSION and
"our" (local OpenWrt trunk) version in PKG_RELEASE.
For local (OpenWrt-only) packages, this implies that those will only
need PKG_RELEASE defined, while PKG_VERSION does not apply following
a strict interpretation. While the majority of "our" packages actually
follow that scheme, there are also some that mix both variables or
have one of them defined but keep them at "1".
This is misleading and confusing, which can be observed by the fact
that there typically either one of the variables is never bumped or
the choice of the variable to increase depends on the person doing the
change.
Consequently, this patch aims at clarifying the situation by
consistently using only PKG_RELEASE for "our" packages. To achieve
that, PKG_VERSION is removed there, bumping PKG_RELEASE where
necessary to ensure the resulting package version string is bigger
than before.
During adjustment, one has to make sure that the new resulting composite
package version will not be considered "older" than the previous one.
A useful tool for evaluating that is 'opkg compare-versions'. In
principle, there are the following cases:
1. Sole PKG_VERSION replaced by sole PKG_RELEASE:
In this case, the resulting version string does not change, it's
just the value of the variable put in the file. Consequently, we
do not bump the number in these cases so nobody is tempted to
install the same package again.
2. PKG_VERSION and PKG_RELEASE replaced by sole PKG_RELEASE:
In this case, the resulting version string has been "version-release",
e.g. 1-3 or 1.0-3. For this case, the new PKG_RELEASE will just
need to be higher than the previous PKG_VERSION.
For the cases where PKG_VERSION has always sticked to "1", and
PKG_RELEASE has been incremented, we take the most recent value of
PKG_RELEASE.
Apart from that, a few packages appear to have developed their own
complex versioning scheme, e.g. using x.y.z number for PKG_VERSION
_and_ a PKG_RELEASE (qos-scripts) or using dates for PKG_VERSION
(adb-enablemodem, wwan). I didn't touch these few in this patch.
Cc: Hans Dedecker <dedeckeh@gmail.com>
Cc: Felix Fietkau <nbd@nbd.name>
Cc: Andre Valentin <avalentin@marcant.net>
Cc: Matthias Schiffer <mschiffer@universe-factory.net>
Cc: Jo-Philipp Wich <jo@mein.io>
Cc: Steven Barth <steven@midlink.org>
Cc: Daniel Golle <dgolle@allnet.de>
Cc: John Crispin <john@phrozen.org>
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-02-24 16:57:38 +01:00
|
|
|
PKG_RELEASE:=12
|
2019-01-27 13:07:52 +01:00
|
|
|
|
|
|
|
|
PKG_SOURCE_DATE:=2018-01-16
|
|
|
|
|
PKG_MAINTAINER:=Hans Dedecker <dedeckeh@gmail.com>
|
|
|
|
|
PKG_LICENSE:=GPL-2.0
|
|
|
|
|
|
|
|
|
|
include $(INCLUDE_DIR)/package.mk
|
|
|
|
|
|
|
|
|
|
define Package/464xlat
|
|
|
|
|
SECTION:=net
|
|
|
|
|
CATEGORY:=Network
|
|
|
|
|
DEPENDS:=@IPV6 +kmod-nat46 +ip
|
|
|
|
|
TITLE:=464xlat CLAT support
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Build/Prepare
|
|
|
|
|
$(call Build/Prepare/Default)
|
|
|
|
|
$(CP) ./src/* $(PKG_BUILD_DIR)/
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Build/Compile
|
|
|
|
|
$(MAKE) -C $(PKG_BUILD_DIR) \
|
|
|
|
|
CC="$(TARGET_CC)" \
|
|
|
|
|
CFLAGS="$(TARGET_CFLAGS) -Wall" \
|
|
|
|
|
LDFLAGS="$(TARGET_LDFLAGS)"
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/464xlat/description
|
|
|
|
|
464xlat provides support to deploy limited IPv4 access services to mobile
|
|
|
|
|
and wireline IPv6-only edge networks without encapsulation (RFC6877)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/464xlat/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/netifd/proto
|
|
|
|
|
$(INSTALL_BIN) ./files/464xlat.sh $(1)/lib/netifd/proto/464xlat.sh
|
|
|
|
|
$(INSTALL_DIR) $(1)/sbin
|
|
|
|
|
$(INSTALL_BIN) $(PKG_BUILD_DIR)/464xlatcfg $(1)/sbin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
$(eval $(call BuildPackage,464xlat))
|
