On 04/04/12 18:35, Dave Rawks wrote: > Not to speak out of turn, but making the build process dependent on a > very specific version of libtools and autotools seems like a really bad > plan. I've never run into a debian source package before that demands to
Only the `bootstrap' step recommends a particular version of autotools. There would be more QA risk if every revision (e.g. 3.3.5, 3.3.6, 3.3.7) was bootstrapped on a different autotools. Given the limited resources of the project, the easiest way to ensure consistency between releases is to make sure that we always bootstrap on a specified platform before making a release tarball. This only impacts people who want to work with source code directly from git (rather than using a tarball) > be built only with specific versions from Debian current stable > (squeeze) especially when the goal of the maintainers appears to be > inclusion into testing/new-stable. Personally I would like for the > entire tarball to have a nice sensible autotools based build install > process "./configure && make && make install" that can be quickly > packaged up with a super minimal amount of distro specific munging. It does do that: someone who downloads the tarball should NOT run the bootstrap script (and should not have to run it). ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
