From: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
---|---|
To: | pgbuildfarm-members(at)pgfoundry(dot)org |
Subject: | [Pgbuildfarm-members] patches for pgbuildfarm client code and docs |
Date: | 2009-11-21 19:27:27 |
Message-ID: | 4ec1cf760911211127x7b4b5b81o37959c5d5484136d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members |
I got the pgbuildfarm client code working the other day; there were a
few rough spots where I had to poke through the code to figure out
what was going wrong, and I thought I'd share some suggestions and
fixes based on my experience.
Here are some issues I've attempted to fix:
* For some reason, the --with-ldap, --with-libxml, and
--with-libxslt get forcibly added in build-farm.conf as configure
options even when config_opts claims to have them turned off. This led
to head-scratching configure errors for me ("error: 'choke'
undeclared") until I noticed the extra flags to ./configure in
configure.log.
* I've tried to clear up the PGBuildFarm-HOWTO.txt in a few places.
I think that it would be helpful to include this file inside the
release tarballs.
* The default CCACHE_DIR points to /home/andrew/... I think this
would be more helpful if initialized to undef, disabling the use of
ccache unless the user fills in this config.
I've attached two patches: one with clean-up for the existing
client-code from CVS, and a separate diff against the existing
PGBuildFarm-HOWTO.txt.
HTH,
Josh
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-11-21 19:32:52 | Re: [Pgbuildfarm-members] patches for pgbuildfarm client code and docs |
Previous Message | Andrew Dunstan | 2009-09-09 22:16:23 | Re: [Pgbuildfarm-members] What's the deal with buildfarm requests? |