On Fri, Mar 16, 2012 at 3:29 PM, Fabian Knittel <fabian.knit...@lettink.de> wrote: > In my opinion, the build defaults should reflect what the project > considers as the recommended defaults - the features we want to see in > every typical OpenVPN server and client.
I strongly against that approach. This is a common mix up between distribution and software project. A software project provides the possibility of using the software in different configurations. A distribution is in charge of the "typical" configuration. Your comment is true for rhel packager, people expect that yum install openvpn will be a "typical" rhel configuration, what exactly this configuration is depends on distribution procedures. Why is lzo different than PKCS#11 or selinux? Which are "typical"? Mind "typical" is probably different between server and client. The software project should not make any assumption of its usage, nor enable/disable features for the sake of best practices instead of proper documentation. Alon.
