Greetings, is there any good reason why building the python module wrapper is not enabled by default?, there will always of course the option of disabling it using --disable-python at configure time but will had the following advantages compared to the current situation :
1) make dist* will always include them as that target will no longer be dependent of what options were used to configure, making bootstrapping simpler and more consistent. 2) the focus of 3.1 is the modular metrics, so having this enabled by default is more consistent with that goal and funny enough it seems it is enabled in our SPEC and in every other document we have. Carlo ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
