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 1oTJIv-0002E3-E1 for pgsql-hackers@arkaria.postgresql.org; Wed, 31 Aug 2022 08:42:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oTJIt-0003HC-Hb for pgsql-hackers@arkaria.postgresql.org; Wed, 31 Aug 2022 08:42:31 +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 1oTJIt-0003H3-7s for pgsql-hackers@lists.postgresql.org; Wed, 31 Aug 2022 08:42:31 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oTJIp-00030b-Pp for pgsql-hackers@postgresql.org; Wed, 31 Aug 2022 08:42:30 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id CCB505C010D; Wed, 31 Aug 2022 04:42:23 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 31 Aug 2022 04:42:23 -0400 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=1661935343; x= 1662021743; bh=5iboNQzghkNLcHOOkAhOajzptFnWVcV6A33YmEX4Qz0=; b=T 1P6MDnh0msu8smgsj6iAtqLGKHMvn7nscjBxvDW7ZwPKU+Usr9IUj+hCQN2UJCts lK5dNrB25pXpLar20JvTZjeWArYFj3CW497CDxV97Lhf/bDF7+dQijJRHS6asv81 wkWAOdh6ZhU2WgevdQjQK71FUsiY3kfzlGKn33du7gvgF8SmNpvqqNZNBShZg0xG jpn2IwtvjB2xeDZgwRER1QrmnUee1UDjgIHUlQac6DkzSdTdk1NlcEAIEuHMSggI IrUIP8WE51Jj+xONm1NO0a5eGxdBkjWB2UYTuIPnwXHX5H7i8/kPzyYOZ2hyGfsk +b5MsWAmefghItc3iIxhw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdekhedgtdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeehleffgeegudejteei hfelteduvdeifffhffdvjedvffegjeekudeludehudeifeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 31 Aug 2022 04:42:22 -0400 (EDT) Message-ID: <15743360-7b79-d04e-0791-d9ccb341dd56@enterprisedb.com> Date: Wed, 31 Aug 2022 10:42:22 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Subject: Re: [RFC] building postgres with meson - v11 Content-Language: en-US To: Andres Freund Cc: pgsql-hackers@postgresql.org, samay sharma , Nazir Bilal Yavuz References: <20211012083721.hvixq4pnh2pixr3j@alap3.anarazel.de> <20220811002012.ju3rrz47i2e5tdha@awork3.anarazel.de> <20220817215317.poeofidf7o7dy6hy@awork3.anarazel.de> <8992c637-0922-8cf8-9188-104153eb3561@enterprisedb.com> <20220820180139.6uj5etquyonz4otf@awork3.anarazel.de> <7dae5979-c6c0-cec5-7a36-76a85aa8053d@enterprisedb.com> <20220824153008.i7pnmh7xilqhsnej@awork3.anarazel.de> From: Peter Eisentraut In-Reply-To: <20220824153008.i7pnmh7xilqhsnej@awork3.anarazel.de> 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 24.08.22 17:30, Andres Freund wrote: >> 0545eec895 meson: Add docs >> >> We should think more about how to arrange the documentation. We >> probably don't want to copy-and-paste all the introductory and >> requirements information. I think we can make this initially much >> briefer, like the Windows installation chapter. For example, instead >> of documenting each setup option again, just mention which ones exist >> and then point (link) to the configure chapter for details. > The current docs, including the windows ones, are already hard to follow. I > think we should take some care to not make the meson bits even more > confusing. Cross referencing left and right seems problematic from that angle. If you look at the current structure of the installation chapter 17.1. Short Version 17.2. Requirements 17.3. Getting the Source 17.4. Installation Procedure 17.5. Post-Installation Setup 17.6. Supported Platforms 17.7. Platform-Specific Notes only 17.1, small parts of 12.2, and 17.4 should differ between make and meson. There is no conceivable reason why the meson installation chapter should have a different "Getting the Source" section. And some of the post-installation and platform-specific information doesn't appear at all on the meson chapter. I think we can try to be a bit more ingenious in how we weave this together in the best way. What I really wouldn't want is two separate chapters that duplicate the entire process. I think we could do one chapter, like - Short Version - Requirements - Getting the Source - Installation Procedure - Installation Procedure using Meson - Post-Installation Setup - Supported Platforms - Platform-Specific Notes Alternatively, if people prefer two separate chapters, let's think about some source-code level techniques to share the common contents.