On Wed, 2007-05-16 at 17:14 -0600, Brad Nicholes wrote: > [Y/N] Remove the external libraries from the repository trunk > [Y/N] Continue to host the external library source in the Ganglia repository > [Y/N] Provide a means (ie. configure, spec files) to build and deploy the > external libraries in a /opt/ganglia location
My opinion would be to remove the external libraries from the trunk, but still provide them as a separate download (and possibly keep them in some other subdir of the ganglia repository). Then there could be something in the instructions that says "if you don't have APR verision >= X, download tarball Y, extract it into sub-directory Z and add the --enable-static-build option". This should only be a temporary solution, and long term I agree w/ Brad that the external libraries should be completely removed. I advocate this simply as a matter of convenience. Given how many systems we have that use RHEL3 or RHEL4, it would be nice for me if Ganglia still provided everything I needed in one spot (even if it is in two tarballs instead of one). I expect that in a year or so, this will be much less of an issue as we upgrade machines. If the external libraries were offered as an extra download, is there any way to track how many times it is downloaded? This could be used as an indicator of when to stop providing the external libs. -- Rick Mohr Systems Developer Ohio Supercomputer Center ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
