Re: release procedure

2009-11-19 Thread Gary V. Vaughan
On Nov 16, 2009, at 5:26 PM, Ralf Wildenhues wrote: Why on earth do we have a commit script that just provides an opaque interface to git? FWIW, I never use it. Gary? Originally, I wrote the commit script simply to automatically pull the CVS commit log message with the ChangeLog, or to

Re: release procedure

2009-11-16 Thread Ralf Wildenhues
Hi Peter, * Peter O'Gorman wrote on Mon, Nov 16, 2009 at 05:16:15PM CET: > For some reason our release procedure calls for running make > distcheck 5 times. This is a tad onerous Agreed. > (one make distcheck takes almost an hour on my system). Hmpf. If you have a multi-way system, try e.g.

Re: release procedure

2009-11-16 Thread Peter O'Gorman
On 11/16/2009 11:29 AM, David Fang wrote: For some reason our release procedure calls for running make distcheck 5 times. This is a tad onerous (one make distcheck takes almost an hour on my system). HACKING asks for: and `make distcheck CC=g++' I think keeping CC=g++ might be a good idea beca

Re: release procedure

2009-11-16 Thread David Fang
For some reason our release procedure calls for running make distcheck 5 times. This is a tad onerous (one make distcheck takes almost an hour on my system). HACKING asks for: and `make distcheck CC=g++' I think keeping CC=g++ might be a good idea because many users (self included) use libl