NAnt boostrapping

Tom "spot" Callaway tcallawa at redhat.com
Wed Feb 24 01:13:32 UTC 2010


On 02/23/2010 08:10 PM, Christian Krause wrote:
> Hello Tom,
> 
> there is currently some uncertainty about bootstrapping NAnt correctly
> and since you've done is a couple of times I thought it would be a good
> idea just to ask. ;-)
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=562729
> 
> If I understood this correctly, it should be done like this:
> 
> 1. build nant with bootstrap=1, get it tagged into buildroot
> 2. build log4net, mono-sharpcvslib, get both tagged into buildroot
> 3. finally build nant with bootstrap=0
> 4. push all new builds
> 
> I'm also unsure whether mono-nunit22 must be built and tagged in step 2
> as well.
> 
> Please can you shed some light on this process? ;-)

I don't think that whole bootstrapping is necessary anymore, with the
new key arrangement, but kalev would be able to shed some light there.

Here are my notes for the old methodology:

Make %{bootstrap} 1 in nant.spec. Minor release increment in nant.spec.
Rebuild. Tag.
Increment release in mono-nunit22.spec. Rebuild. Override tag.
Increment release in log4net.spec. Rebuild. Override tag.
Increment release in mono-sharpcvslib.spec. Rebuild. Override tag.
Reset %{bootstrap} to 0 in nant.spec. Major release increment in
nant.spec (drop minor). Rebuild.

Remove all override tags.
Tag latest builds for $BRANCH-final.

~spot


More information about the mono mailing list