On Mon, Mar 19, 2012 at 11:48 AM, David Sommerseth <openvpn.l...@topphemmelig.net> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 19/03/12 10:42, Gert Doering wrote: > > Hi, > > > > On Mon, Mar 19, 2012 at 10:38:32AM +0100, David Sommerseth wrote: > >> On 19/03/12 10:01, David Sommerseth wrote: [...snip...] > >>> > >>> On a related note: --enable-iproute2 > >>> > >>> Should we also expect this to be available on all *nix platforms? > >>> iproute2 has been available on most platforms I know of for a > >>> very long time, and is superior net-tools in very many ways. > >> > >> I've been educated by Gert now, and learned that iproute2 is not > >> common on most Unix based platforms, but is a Linux oriented tool. > >> So this suggestion makes no longer much sense. > > > > Actually, I still agree with you that enabling it by default on Linux > > is the way forward. > > > > (Or hook into the netlink interface directly, but I'm not sure > > whether this will lead to easier to understand code, and easier to > > read log files, than what we have now - where you could, for testing, > > run the commands manually to see which ones cause problems) > > I agree, but I consider that a packager responsibility. I don't think we > should have different defaults in our build tools based on which platform > you build on. That will easily get much more chaotic in the long run to > maintain properly, especially if you take into consideration cross > compilation (like building Windows binaries on Linux).
The only component that is in question is lzo. I still think this is packager responsibility, not sure why this is an exception. But if it will make people happy, I will enable lzo by default. All the other components are optional by they nature, and again it is up to packager to decide what good for his configuration. Alon.
