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 1pUkQi-0003O4-Dc for pgsql-docs@arkaria.postgresql.org; Wed, 22 Feb 2023 08:24:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pUkQg-0006Tp-Vq for pgsql-docs@arkaria.postgresql.org; Wed, 22 Feb 2023 08:24:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pUkQg-0006Tg-Nh for pgsql-docs@lists.postgresql.org; Wed, 22 Feb 2023 08:24:46 +0000 Received: from new2-smtp.messagingengine.com ([66.111.4.224]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pUkQd-0007wc-MD for pgsql-docs@lists.postgresql.org; Wed, 22 Feb 2023 08:24:45 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id A1E5D582038; Wed, 22 Feb 2023 03:24:39 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 22 Feb 2023 03:24:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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=1677054279; x= 1677061479; bh=gbE2oDuH1ESrNOZ4s+5Qhm6MAx/qgs6D9932vktibVk=; b=H 5ZBIONyf+i1iu0nslevOgVF8xCEOUQmfY6lTGipZgJtnVeiJghDAleXfs8gJpLdK lu/hsoLPcxTlYgeRrwFo6+/4KZDAzCMC40bMeqG2oe23QGnKZZF9STHAFotNF7/2 tDbmRiDOCJw2954Os4vTl1HUr5V17ZjG1bhZOQVJOtxadk9JNvVGdo7895pBUb7+ df0A4CCShkJahkbhhwxi+Oy8/811GvYujQmOHPGKHMwjFR4LKrZcL7qCev0AvKyb KycwHmrWwTVF4j4R34M/mySxw69DHk9WDODmrZXsfq08tXys+hbl/rtLrdcQMOM6 b2Ch249sMLmr5YxDC3EJw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudejkedgudduiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttdefjeenucfhrhhomheprfgv thgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnh htvghrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepheelffeggedujeet iefhleetuddvieffhfffvdejvdffgeejkeduleduheduieefnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgr uhhtsegvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 22 Feb 2023 03:24:38 -0500 (EST) Message-ID: <54d82c8c-12a5-be8e-f340-408c171eb256@enterprisedb.com> Date: Wed, 22 Feb 2023 09:24:37 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Add missing meson arguments in docs Content-Language: en-US To: Michael Paquier , Jelte Fennema Cc: pgsql-docs@lists.postgresql.org References: From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 22.02.23 02:57, Michael Paquier wrote: > -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. Yeah, this is just in the long tail of things to work through.