Michael Glaesemann wrote:
On Jul 27, 2005, at 11:27 AM, Andrew Dunstan wrote:
I have reduced some of the clutter from OS names/versions and
compiler names/versions,
Out of curiosity, how did you do this? Did you update the original
registration data or make some kind of mapping?
Fi
Larry Rosenman wrote:
I'd also like to see a way to run both --enable-debug and not --enable-debug
runs either alternately or
With a command line arg.
Same with the --enable-integer-datetimes switch.
In general we don't want you changing the settings much. That goes to
the issue of
On Jul 27, 2005, at 11:42 AM, Larry Rosenman wrote:
Given the current issue with the SCO Optimizer and --enable-debug,
I'd like
to keep it on the list.
I'd also like to see a way to run both --enable-debug and not --
enable-debug
runs either alternately or
With a command line arg.
Same wi
On Jul 27, 2005, at 11:27 AM, Andrew Dunstan wrote:
I have reduced some of the clutter from OS names/versions and
compiler names/versions,
Out of curiosity, how did you do this? Did you update the original
registration data or make some kind of mapping?
and can reduce some more in the st
Given the current issue with the SCO Optimizer and --enable-debug, I'd like
to keep it on the list.
I'd also like to see a way to run both --enable-debug and not --enable-debug
runs either alternately or
With a command line arg.
Same with the --enable-integer-datetimes switch.
Just my $0.02
Andrew Dunstan wrote:
At one stage I thought of stealing some vertical space for 8 or 10
columns of 10 pixels or so to show the state of the most importand
build flag. I still might do that, if I can standardise the OS and
Compiler info so that they get shorter (e.g. is just knowing that we
On Mon, Jul 25, 2005 at 07:06:33PM -0400, Andrew Dunstan wrote:
> >Well, the config options are always sent back in status reports... maybe
> >if there was just a summary page that listed what those options were on
> >a per-report basis; or even maybe diffing between reports to show
> >changes.
> >
Jim C. Nasby wrote:
On Mon, Jul 25, 2005 at 08:49:45AM -0400, Andrew Dunstan wrote:
We don't consider configuration settings ( e.g.
--enable-integer-datetimes or --with-perl) to be part of the
personality, and we don't currently track changes in them, nor in
versions of third party libra
On Mon, Jul 25, 2005 at 08:49:45AM -0400, Andrew Dunstan wrote:
> We don't consider configuration settings ( e.g.
> --enable-integer-datetimes or --with-perl) to be part of the
> personality, and we don't currently track changes in them, nor in
> versions of third party libraries we might use (
Tom Lane wrote:
One pretty silly point: I notice that
http://www.pgbuildfarm.org/index.html
says "The build farm software does not currently run on Windows".
This is out of date no?
Fixed, thanks.
One not so trivial question: do we have a policy about system/compiler
updates on buildfar
One pretty silly point: I notice that
http://www.pgbuildfarm.org/index.html
says "The build farm software does not currently run on Windows".
This is out of date no?
One not so trivial question: do we have a policy about system/compiler
updates on buildfarm members? Arguably, if I'm running say O
11 matches
Mail list logo