Date: Fri, 3 Nov 2023 20:19:18 +0100
From: Christoph Berg <myon@debian.org>
To: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
	Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>,
	pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: meson documentation build open issues
Message-ID: <ZUVHttJNHalXcUNx@msg.df7cb.de>
Mail-Followup-To: Christoph Berg <myon@debian.org>,
	Andres Freund <andres@anarazel.de>,
	Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
	Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>,
	pgsql-hackers <pgsql-hackers@postgresql.org>
References: <3fc3bb9b-f7f8-d442-35c1-ec82280c564a@enterprisedb.com>
 <7137c5b3-7d9e-4659-03a2-9e2df74cbab7@enterprisedb.com>
 <20230405144512.zfzb6vd77dk5dnyr@awork3.anarazel.de>
 <50193d79-e7d1-ea81-1ef3-5670b007c7c3@enterprisedb.com>
 <c3e12a10-5824-f9c7-ad09-c66720df7b2d@dunslane.net>
 <b2437a6f-b083-5abe-6bdf-f5968a666992@enterprisedb.com>
 <ZUUC_T52xTbaXRys@msg.df7cb.de>
 <20231103163848.26egkh5qdgw3vmil@awork3.anarazel.de>
 <ZUU5pRQO6ZUeBsi6@msg.df7cb.de>
 <20231103185344.zhfzturwdbp4d4s5@awork3.anarazel.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20231103185344.zhfzturwdbp4d4s5@awork3.anarazel.de>
Archived-At: 
 <https://www.postgresql.org/message-id/ZUVHttJNHalXcUNx%40msg.df7cb.de>
Precedence: bulk

Re: Andres Freund
> The reason for that is simply that the docs take too long to build.

That why I'd prefer to be able to separate arch:all and arch:any
builds, yes.

> The summary does include both. LLVM is 'llvm', man/html docs is 'docs' and pdf
> docs as 'docs_pdf'.

Sorry, I should have looked closer. :(

> The following is *not* an argument the docs targets shouldn't be documented
> (working on a patch), just something that might be helpful until then /
> separately. You can see which targets are built with
> 
> ninja -t targets all|grep doc/src/

Thanks.

> > Oh, that's a showstopper. I thought meson would already be ready for
> > production use. There is indeed an "experimental" note in
> > install-requirements.html, but not in install-meson.html
> 
> I'm working on merging it. Having it for core PG isn't a huge difficulty, the
> extension story is what's been holding me back...

In-core extensions or external ones?

> > Why isn't it "auto" like the others?
> 
> I don't really remember why I did that, but it's platform specific, maybe
> that's why I did it that way?

Isn't that kind the point of autodetecting things? Aren't bonjour and
bsd_auth autodetected as well?

> > > I don't think the autoconf build currently exposes separately configuring
> > > pkglibdir either, I think that's a debian patch? I'm entirely open to adding
> > > an explicit configuration option for this though.
> >
> > That would definitely be helpful.
> 
> I have a patch locally, will send it together with a few others in a bit.

Thanks!

Christoph