On Sun, Dec 06, 2009 at 09:28:04AM +, Daniel Pocock wrote:
Carlo Marcelo Arenas Belon wrote:
On Wed, Nov 25, 2009 at 11:00:21AM +, Daniel Pocock wrote:
b) should the choice of bootstrap environment be locked for all
3.1.X, and only changed when increasing the minor version number
(e.g. when we go from 3.1 to 3.2)?
no, but since our build system is full of hacks and not completely reliable
it might be a good idea to test no issues are introduced when looking at
a new version.
Ok, but if it is not locked down, let's consider some of the following:
- document the version we expect
agree, and that is what README.SVN is for, but first we have to decide which
version to expect to begin with.
- maybe add some check to configure that warns if a different version of
autotools is detected?
configure doesn't depend autotools and so that would be the wrong place to put
any checks, but configure.in does and there is where bootstrapping should be
aborted using AC_PREREQ and friends if using the wrong versions.
c) what environment should be used to bootstrap 3.2.X/trunk?
the same than 3.1 so that all improvements in the build system will be
tested there and then backported for stability.
Not necessarily - changes can be backported and then tested on the
release branch before it is frozen/tagged for a release candidate.
this will violate your rule of same autotools per branch but frankly I
don't care as far as we allocate for the extra time that will be needed to
certify the new bootstrap environment works.
That would allow more aggressive changes to be implemented in trunk that are
not intended for backport.
trunk has several changes that are not intended for backport already and they
are not intended for release either or we will have a 3.2 branch already.
d) Can anyone volunteer to provide a stable bootstrap environment
(e.g. a virtual server) just for Ganglia? Two such environments may
be needed, one for trunk and one for the current release branch.
Matt did offer an EC2 instance if we could agree on an OS version :
http://www.mail-archive.com/ganglia-developers@lists.sourceforge.net/msg05271.html
I suggested Debian 5.0 (more conservative) or Fedora 12 (to be updated more
frequently) but as far as it is agreed, documented and reproducible anything
should work.
I prefer Debian 5.0 (lenny), that is what I have on my laptop, home PC
and various other infrastructure that I use. Elsewhere I am using
RHEL3/4/5.
Debian 5.0 is also what is being used for bugzilla AFAIK and so that might
be a good option for consolidation.
We also have access to the OpenCSW build farm, and they are willing to
consider applications for access by Ganglia developers, so we could look
at that as a bootstrap environment.
Bootstrapping is done only once per package and so wouldn't make sense to
also do bootstrapping in Solaris.
having the OpenCSW build farm as part of our test builds would be a great
way to ensure Solaris users are better supported though.
Carlo
--
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers
