I know when we discussed this at the meeting a couple of weeks ago, the consensus was to leave libconfuse in the repository. I am in the middle of reworking configure.in in order to remove APR yet still allow for --enable-static-build. Everything works up to the point of 'make dist' or 'make distdir'. For some reason, no matter what I do, the srclib/confuse directory is not included in the tarball. This leads me back to asking the question, should we remove libconfuse from the repository as well? I believe our reasoning for leaving it in was because libconfuse is not a commonly distributed library on many distros. However, the only purpose of retaining libconfuse (or APR, expat) in the SVN repository, is for static builds. If we are going to continue to support static builds, then I would suggest that we document how a static build is done (which I think we agreed to do anyway). In order to do a static build, the user has to download and expand the apr and expat so urce tarballs to the srclib directory. I don't see having to download and expand libconfuse into srclib as any more work. We will obviously provide as part of the doc, links to these tarballs. Given that, is there any reason why libconfuse needs to remain in our repository? And even if we agree to keep it in the repository, is there any reason to continue to include it as part of the Ganglia distribution tarball?
Brad ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
