Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pUeOM-0000HC-Lv for pgsql-docs@arkaria.postgresql.org; Wed, 22 Feb 2023 01:57:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pUeOL-0004zq-GW for pgsql-docs@arkaria.postgresql.org; Wed, 22 Feb 2023 01:57:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pUeOL-0004zf-8w for pgsql-docs@lists.postgresql.org; Wed, 22 Feb 2023 01:57:57 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pUeOH-0004qI-0I for pgsql-docs@lists.postgresql.org; Wed, 22 Feb 2023 01:57:56 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B72C05C0199; Tue, 21 Feb 2023 20:57:51 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 21 Feb 2023 20:57:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1677031071; x=1677117471; bh=D/8ABVDkgj JG1jFTQWPYck8BXIwRluS8tTBYASMncD4=; b=EEsZb0bfjQkvsTvkWXTbSuOgz3 slri5Fa9rk+ZLxiIwynoXCubzOrJfOry46FZ4g/pm17sJhdrv1lXcN058+VvKS7s xp5SADtVpHIjfwVSnAjIHbCjSz/cSQuuVR+p9W8CuDqIjbK2XjhCeEKmSyON9Yag CZD+Qyv4xzlHJmKeE5nvZPlgAOE+zJXAfsGwznKghEfE7EnidkiHc9CWC17R37PV asUWTDxQKrJX5Ry0SlZmWCQRL8+7Lvy2t+nvCmUbdvklQCNMhm82GDcw3mvGTmVI 056kISgrc6TavpEyXoydMGxR9lRTYl1ySw9sm1F88tDJzDJDZ3/QQmQ+5A1A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1677031071; x=1677117471; bh=D/8ABVDkgjJG1jFTQWPYck8BXIwR luS8tTBYASMncD4=; b=f+GPVGZ3LpLjS36aQcyV1DTayrdKp/Yb7c+qOA6/W0kx 0/7Eii5lt26qIILl8G++M4nYI2e48Ko7Dos+KQAcfMlzUcvgl7gf9sCSDwb+/vcL tOqmpkIuIyz785vAnTtumnBZ7dgOsMjuktFuRnHE/Ujbfr0P3TTLFI09mBop3cGx J7rylDRqtg/4ftfmtxnRNc1doTYNE547hW/YnojsEXFUHcLNW41/BUBW1n/9uCdI xMMhEMhsa1yEuk47eibUhZ/CBRQgXRFOk+duTA2nFeo1Ss57vLBtS7ZP/QsQWKd6 jkyAG1Y65JCymxKw59CQjJeDM+4uHPHMqy+T1b6ykQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudejkedgfeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdlfeehmdenucfjughrpeffhf fvvefukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghq uhhivghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvg hrnhepgeffjeevgfevuddvjedtvddtieejheduueelvddufedtgfefjedvkeevkeeivddv necuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghr rdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 21 Feb 2023 20:57:50 -0500 (EST) Date: Wed, 22 Feb 2023 10:57:47 +0900 From: Michael Paquier To: Jelte Fennema Cc: pgsql-docs@lists.postgresql.org Subject: Re: Add missing meson arguments in docs Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="4l2YrbNAM0o1NpA/" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --4l2YrbNAM0o1NpA/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Feb 21, 2023 at 10:40:12AM +0100, Jelte Fennema wrote: > The -Dcassert and -Db_coverage of the meson build didn't show in the > docs that they needed to be passed true or false. All other options > specified the arguments they expected. This patch fixes that. Indeed, values have to be specified after the equal sign of each option, so applied what you are suggesting here. -Db_coverage is part of the core options of meson because it is not listed in meson_options.txt, no? Documenting the switch is fine, but it seems like we lack contents here. The paragraph describing -Db_coverage links to regress-coverage, still this only has instructions for ./configure. Shouldn't we have some docs to show one how to achieve the same with meson? I'd guess that a separate section for meson would make the most sense, for as long as we support both methods in parallel. https://wiki.postgresql.org/wiki/Meson tells nothing about that, for one. -- Michael --4l2YrbNAM0o1NpA/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmP1dpsACgkQnvQgOdby QH1k2BAAiMBAljK+F9igBOmSBxA9SAO+4Ym+w8w4FIPwCJXIGxAoLiEQjkKu0vp0 ER084AYb2Zp3CGZyClK7zNtojvmEi7wk9iccSmZZTjzsSrsu5UXOLxkjAbtj29ro Yle3ozX4cW+Vr379jWXtmY/mZiSO08NJG67NJbWSvbomhoGspiYhZrFcR5czOmpn mXhAZwPHRZhSQMIHp2gjjxbOlANDXm2BxC92nm3TATdbBYVpwPa66RlBFY0QNE86 dxMx5DcT+uaE0NKFAIHSNd6HF4GUWOYcw69RVySFUdZtk84Y2b7gYqPjk00aJtEi ga1CoZYR6vsFL/KVQIiMAY7EYbX8+2MmpGcRkQYQdvw4ndNR4BmD/oc1wzYRUwAm 0NjlVDNT6R1Y0XAAu/qRR2fZ84Iz8wu7rFu1OQQZlDf1xnTpjpa1VdsaReG6FIgg h8iWuO1M/OX+XHkOCtJ+zgFJQxeLotAPeRUMw9UcbRUV82NuK0cCNj6PQQ0kDKns 6u+KHy5SheEsdUDDshZm7vAuFnVTwKWndWeIBp972hlB9FQBEBzeVR59xnRvRiiO EaMj4l7ysHU4oCN4/7CQTkt7uePwMMrIDXsHmaeRdHGOrFdd/MJzF22RpYKmMGt8 S5hZT1dlSDulSvUoWo+p+tZ6rvpaQF7q/f0S1iBsWDVzu0KUTcg= =ljBC -----END PGP SIGNATURE----- --4l2YrbNAM0o1NpA/--