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 1q26Oh-0001Us-LQ for pgsql-hackers@arkaria.postgresql.org; Thu, 25 May 2023 08:32:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q26Og-0002IC-CU for pgsql-hackers@arkaria.postgresql.org; Thu, 25 May 2023 08:32:34 +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 1q26Oe-0002I2-RZ for pgsql-hackers@lists.postgresql.org; Thu, 25 May 2023 08:32:33 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q26OX-001mvr-GY for pgsql-hackers@postgresql.org; Thu, 25 May 2023 08:32:31 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id AF7D13200A3E for ; Thu, 25 May 2023 04:32:22 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 25 May 2023 04:32:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:message-id:mime-version:reply-to :sender:subject:subject:to:to; s=fm3; t=1685003542; x= 1685089942; bh=bUeiq/QeJ7ID5T26Sb3MxV9XVWXrcduO6F4QSV7yRcs=; b=X zuXSmnCSb+J4BFj/jV0PW0eDfSPeL/s+MGY7w7P4zF38JcnKJGTq3Z+JptjrF9Ak zgkcl9JMq8zCHNYWPpMrW2QRl6o8eb9O5C/HCT2o3wlSIlV7HG/wN3Sblequ6sex 4wmGmGYf4EdYjBbcoxu7ofva9a+Ev/Q9nIy9qOKMaCAh6qt7cnuR4PcGnnSHEGK+ FFYFVIRUxEeabu4HMr3WTDO0w2mSMMupXapTn3UiUQKiH8bv3PK/SkEXnXnQNwJn HEk9mdTRBZEE5rClW/SGWsdqzXc1Jxh4cOE3SsQNuCYi6DZNzToikDTtPGOGihrQ Bg2AUmBZzAgjIS+q57rJA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:message-id:mime-version: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=1685003542; x=1685089942; bh=bUeiq/QeJ7ID5 T26Sb3MxV9XVWXrcduO6F4QSV7yRcs=; b=kx/csXHCYJDMdN1cNTYViyfMdI7qX B/eOJ2+XRHsbQOKYwgEi0zE2hWMUuEMW9RcU6s+DgsbsAsjGfxXBhqrjqGR9BQZQ vTezQU0Q8g6uYGJIGtlIqyLUehIxDHVpiRQAR1JRJvlxGvMB05OECd3K6vXK+8u+ 2tqDB2H3HIFYfnDoJwo4laerV+kUIRs+e8+zXmX/63lZZkyV1kYZYUn8bRayXOdQ Ng056rKI66TFl5DeyLN1F3mCoZ2WdI9xeTUJzwn7pycbFKDlOKWx9PgEmeaof7+r 6KqfRed3U7FhZSpxzBTmplpoNi2mY5N1YrxNv0ejqw2EI9Gj3VdzxHm/w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeejjedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfhuffvtgfgsehtjeertd dtfeejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghrsegv ihhsvghnthhrrghuthdrohhrgheqnecuggftrfgrthhtvghrnhepgefgieetfeeiueeike eiheehteeigfejgeejieelfeekgeffgfffgfeuhfeujeeknecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhesvghishgvnhhtrhgruh htrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 25 May 2023 04:32:21 -0400 (EDT) Message-ID: Date: Thu, 25 May 2023 10:32:20 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Content-Language: en-US From: Peter Eisentraut Subject: Why does pg_bsd_indent need to be installed? To: pgsql-hackers 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 Why does pgindent require that pg_bsd_indent be installed in the path? Couldn't pgindent call the pg_bsd_indent built inside the tree? That would make the whole process much smoother.