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 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.
I'm no genius code slinger when it comes to build workflows, but what we have now just doesn't feel like what I would expect from a software package as mature and widely used as ganglia. -Dave On 04/04/2012 08:58 AM, Bernard Li wrote: > Hi Stu: > > I am not too familiar with Debian and Ubuntu packaging but I just wanted > make sure you and Jeff are aware of each other's work. Obviously we do > not want any duplicated efforts. :) > > Going forward do you guys have any recommendations on how we can improve > the Debian packaging files within our repository such that anybody > downloading our official tarballs could build Debian packages out of it? > > Many thanks! > > Bernard ------------------------------------------------------------------------------ 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
