Skip site navigation (1) Skip section navigation (2)

Re: PG documentation build is wedged

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: PG documentation build is wedged
Date: 2011-11-24 20:45:07
Message-ID: 4ECEACD3.4020000@kaltenbrunner.cc (view raw or flat)
Thread:
Lists: pgsql-docs
On 11/24/2011 09:16 PM, Alvaro Herrera wrote:
> 
> Excerpts from Andrew Dunstan's message of jue nov 24 14:44:18 -0300 2011:
> 
>> You need to change the config of this animal to something like:
>>
>>      optional_steps => { build_docs => { branches => [ 'HEAD' ], 
>> min_hours_since => 0 } },
>>
>>
>> There's no point in not building the docs for HEAD on every build, since 
>> "make dist" in the new module will build them if they're not built 
>> anyway, but in such a way that they're not so readily usable, whereas 
>> this way you can copy them out easily.
> 
> FWIW while updating this config I noticed that we have --with-ldap on
> HEAD and 8.2, but not the other branches; and --with-xml only in HEAD
> and 8.3 but not the other branches.  I assume this is from the stock
> config file (snippets below).
> 
> It seems to me that the BF stuff should have some operator to specify
> "any branch newer than X".

not sure I follow at all...

> 
> 
> # ldap support is new as of 8.2
> if ($branch eq 'HEAD' || $branch ge 'REL8_2')

this basically means "do only if $branch is exactly HEAD or if $branch
is greater or equals to REL8_2 which is exactly what you are proposing
and what actually makes sense?


Stefan

In response to

Responses

pgsql-docs by date

Next:From: Alvaro HerreraDate: 2011-11-24 21:07:36
Subject: Re: PG documentation build is wedged
Previous:From: Heikki LinnakangasDate: 2011-11-24 20:30:16
Subject: Re: Abount max_stack_depth's default value

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group