Sorry... [1] http://thread.gmane.org/gmane.network.openvpn.devel/5772/focus=5947
2012/3/16 Alon Bar-Lev <alon.bar...@gmail.com>: > Hello, > > Part of the reasoning was discussed here[1]. > > If we do not want to do auto detection, enabling optional components > may lead to configure failure, and force the user to explicitly > disable this feature. > > It is possible, and I don't mind so much, however, I prefer configure > to use the minimum absolutely needed components by default, and in > majority of valid cases succeed. > > Disabling by default does not effect users nor building via build > script nor building via package management (rpmbuild, deb). It only > effects people who build manually from sources. These people should > not only consider the lzo enable/disable but many more configure > options so lzo is no exception. > > Alon. > > [1] http://thread.gmane.org/gmane.network.openvpn.devel/5772/focus=5811 > > 2012/3/16 Samuli Seppänen <sam...@openvpn.net>: >> Hi all, >> >> In yesterday's meeting we reviewed this patch >> >> PATCH 39/52 build: proper lzo detection and usage >> URL: http://thread.gmane.org/gmane.network.openvpn.devel/5772/focus=5811 >> >> The patch was ACKed, but there was disagreement whether LZO should be >> enabled or disabled by default. Whichever the case, it will only affect >> people building OpenVPN, not the end-users. Official builds will continue to >> have LZO support. >> >> Opinions? >> >> -- >> Samuli Seppänen >> Community Manager >> OpenVPN Technologies, Inc >> >> irc freenode net: mattock >> >> >> ------------------------------------------------------------------------------ >> This SF email is sponsosred by: >> Try Windows Azure free for 90 days Click Here >> http://p.sf.net/sfu/sfd2d-msazure >> _______________________________________________ >> Openvpn-devel mailing list >> Openvpn-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
