The swanctl feature is not needed in IPFire right now,
but we want to use IPSECKEY in the future.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
name = strongswan
version = 5.3.3
-release = 2
+release = 3
groups = Networking/VPN
url = http://www.strongswan.org/
flex
gmp-devel
gperf
+ ldns-devel
libcap-devel
libcurl-devel
libgcrypt-devel
perl
sqlite-devel
systemd-devel >= 221-2
+ unbound-devel
end
configure_options += \
--enable-eap-mschapv2 \
--enable-eap-identity \
--with-capabilities=libcap \
- --enable-swanctl \
+ --enable-unbound \
--enable-systemd
if "%{DISTRO_ARCH}" == "i686"
script postup
systemctl daemon-reload >/dev/null 2>&1 || :
systemctl reload-or-try-restart strongswan.service >/dev/null 2>&1 || :
- systemctl reload-or-try-restart strongswan-swanctl.service >/dev/null 2>&1 || :
end
script preun
systemctl disable --no-reload strongswan.service >/dev/null 2>&1 || :
- systemctl disable --no-reload strongswan-swanctl.service >/dev/null 2>&1 || :
systemctl stop strongswan.service >/dev/null 2>&1 || :
- systemctl stop strongswan-swanctl.service >/dev/null 2>&1 || :
end
script postun