From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | pgbuildfarm-members(at)pgfoundry(dot)org |
Subject: | Re: [Pgbuildfarm-members] release 2.12 of client code |
Date: | 2006-01-02 16:33:17 |
Message-ID: | 43B955CD.8000103@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members |
None of it. I try to avoid the need for config file upgrades where
possible. If it is needed, I will mention it in the release note. Maybe
I should also mention if a config file upgrade is not necessary.
cheers
andrew
Jim C. Nasby wrote:
>How much of this is just config file changes?
>
>It would be easier for upgrades if there was a stock distribution config
>that had good defaults that were then over-ridden by site-specific
>settings as needed. That way, config changes wouldn't need to be
>manually added to existing installs.
>
>On Thu, Dec 29, 2005 at 12:31:49PM -0600, Andrew Dunstan wrote:
>
>
>>Now available.
>>
>>See http://pgfoundry.org/frs/?group_id=1000040
>>
>>
>>Changes:
>>. don't send log tar if the failure is from CVS stage - the files would be
>>from an earlier run.
>>
>>. report changed files for forced run
>>
>>. Add "use warnings"
>>
>>. add NO_LOCALE flag for check target - still issues on postgres side ;-(
>>
>>. add db logfile extract to stop/start logs
>>
>>. minor bug fixes
>>
>>. add update_personality.pl script
>>
>>
>>cheers
>>
>>andrew
>>
>>
>>_______________________________________________
>>Pgbuildfarm-members mailing list
>>Pgbuildfarm-members(at)pgfoundry(dot)org
>>http://pgfoundry.org/mailman/listinfo/pgbuildfarm-members
>>
>>
>>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-01-06 17:21:16 | [Pgbuildfarm-members] SOAP interface |
Previous Message | Jim C. Nasby | 2006-01-02 16:03:05 | Re: [Pgbuildfarm-members] release 2.12 of client code |