[arch-dev-public] Preparing OpenVPN 2.4.x - possible incompatible changes

[Christian Hesse]

Hello everybody,

a new OpenVPN stable release is being prepared, namely version 2.4.0.
Currently we have 2.4_beta2. I think about making changes to our package that
require user intervention.

We shipped a systemd unit file before OpenVPN upstream had one. Upstream now
has unit files, but two (for server and client) instead of just one. I did
backport some security features for our unit, but refused to migrate to the
upstream solution within the 2.3.x branch.

That could change with 2.4.0. Instead of openvpn at .service we would have
openvpn-server at .service and openvpn-client at .service. Additionally the
'daemon' option is no longer allowed with the upstream units.

Any opinion about this change? Who can post news about this on the website?

Stumbled about another fact... We define PLUGIN_LIBDIR, that allows to use
relative paths from that directory in configuration to call the plugins. This
path is '/usr/lib/openvpn' - plugins are installed to
'/usr/lib/openvpn/plugins', though. Any reason for that?
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20161126/9c7e48e0/attachment.asc>