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 1pbbed-0005eG-Te for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Mar 2023 06:27:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pbbec-0001Sy-LK for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Mar 2023 06:27:30 +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 1pbbeb-0001Sp-Ju for pgsql-hackers@lists.postgresql.org; Mon, 13 Mar 2023 06:27:30 +0000 Received: from wnew1-smtp.messagingengine.com ([64.147.123.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pbbeX-00039n-Tl for pgsql-hackers@postgresql.org; Mon, 13 Mar 2023 06:27:29 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.west.internal (Postfix) with ESMTP id 34E8B2B06722; Mon, 13 Mar 2023 02:27:22 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 13 Mar 2023 02:27:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type: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=fm2; t= 1678688841; x=1678696041; bh=BrWbceH0Zp6W9ZUaAuSGbYeQ14e0odYTU4c ZiuV5DWU=; b=KrCapLKSF7aCfZdyHZEESl0wbAmM8+eZouC0RC5FFy9erJ05ePj T7fAr7UqMpRGm3xquF5J8EkICBATN4dTh6j3ztDwfelmx5Ma0rYuIEvmP5hWidw/ XED0iKG5d1MHOn+0KLtkOU1xpOZzflqPdt99VpSTaHykWDC0ISlqMC7rZNSJXwKx 462CfmUwQqULCwMBfJnR4GZQQn0eWucphTQAfpU6vLtQuLTuEPd1ClRIemVSyEKB PSlMRbNhcvJnhHw4sUM8x8HoAgIyZN3lS0AnK8/yn5+L2rr5YG89s3XheZwnxnG7 zkLXZG5EBfwT/jmlp5NNr6pYi76em6aTc8g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddvfedgledvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeehleffgeegudejteei hfelteduvdeifffhffdvjedvffegjeekudeludehudeifeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 13 Mar 2023 02:27:20 -0400 (EDT) Message-ID: <6d3310fb-50e3-34d8-fe10-8dd8c4ffdf23@enterprisedb.com> Date: Mon, 13 Mar 2023 07:27:18 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: meson: Non-feature feature options To: Daniel Gustafsson Cc: Nazir Bilal Yavuz , Andres Freund , PostgreSQL Hackers References: <20230208162310.scllwgr5qp3m5tme@awork3.anarazel.de> <000d58dd-6164-f695-fe12-38ac7e37543b@gmail.com> <1d1eb740-e2d6-dd92-ba35-985af38b30d5@enterprisedb.com> <20230220194249.lkirdwhosjq6zdkc@awork3.anarazel.de> <4e1fcc8d-77cf-082c-5dd8-9ab09bb7a05f@enterprisedb.com> <0fff0827-c1f5-d29c-2ee3-dc8c871176bf@enterprisedb.com> <9df9067d-5651-2d3e-e838-9e5d273f5524@enterprisedb.com> <5250E85B-4A97-4DA1-8900-7DCDE925441A@yesql.se> Content-Language: en-US From: Peter Eisentraut In-Reply-To: <5250E85B-4A97-4DA1-8900-7DCDE925441A@yesql.se> 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 09.03.23 14:54, Daniel Gustafsson wrote: >> On 9 Mar 2023, at 14:45, Peter Eisentraut wrote: > >> How about we just hardcode "openssl" here instead? We could build that array dynamically, of course, but maybe we leave that until we actually have a need? > > At least for 16 keeping it hardcoded is an entirely safe bet so +1 for leaving > additional complexity for when needed. I have committed it like this. I didn't like the other variants, because they would cause the openssl line to stick out for purely implementation reasons (e.g., we don't have a line "compression: YES (lz4)". If we get support for another ssl library, we can easily reconsider this.