Carlo Marcelo Arenas Belon wrote:
> On Sun, Dec 06, 2009 at 09:28:04AM +0000, Daniel Pocock wrote:
>   
>> Carlo Marcelo Arenas Belon wrote:
>>     
>>> On Wed, Nov 25, 2009 at 11:00:21AM +0000, 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.
>
>   
Ok, should we use AC_PREREQ for 3.1.6, are there any disadvantages?

>
>   
>>>> 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/[email protected]/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.
>   

Who controls access to the Bugzilla server?  I wouldn't mind having use 
of that as a bootstrap environment.

>   
>> 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.
>   
No, I wasn't suggesting we bootstrap separately for Solaris.  I was just 
suggesting that we use the OpenCSW machine to bootstrap for all platforms.

However, we would be stuck with whatever version of autotools is current 
in the OpenCSW environment, and any decision to change the version there 
would be out of our control.

I think Debian 5.0 (lenny) is the final decision then - any final 
objections/comments?

Should we

a) after fixing the other showstopper (fork issue), do we tag 3.1.6 and 
let people test a tarball from Debian 5 autotools?, or

b) make another 3.1.5 tarball using Debian 5 autotools, and put it in a 
separate location for people to test before we tag?

Do we have a list of environments that must be tested after changing 
autotools again?


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Ganglia-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to