On Wed, Mar 12, 2008 at 11:09:22AM -0600, Brad Nicholes wrote:
>    I know when we discussed this at the meeting a couple of weeks ago, the 
> consensus was to leave libconfuse in the repository.

I mentioned a week ago, also, after removing expat from srclib, that
leaving confuse in the repository wasn't really going to accomplish anything but
complicate the static builds, as you concluded as well.

  
http://www.mail-archive.com/[email protected]/msg03710.html

>  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.

updated README.svnusers with the instructions at that time too; you NEED to use
--enable-static-build after the initial bootstrap for it to be included.

> This leads me back to asking the question, should we remove libconfuse from
the repository as well?

Either remove libconfuse or put back all libraries and keep using
--enable-static-build as it was designed.

Since leaving apr also indirectly implies having support for apr 0.9 in the
code then it should be probably better to remove confuse.

> 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.

static builds, don't really need --enable-static-build, and could be done
without any libraries in srclib and using --with-{apr,expat,confuse} and
--enable-static (it might require some other fixes as well)

> 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 source tarballs to the srclib directory.

no, this would force as to keep all the "enable-static-build" logic and
maintain it (which has been found to be broken in HEAD too frequently to be
considered reliable)

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to