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 1q4w3I-000498-Jm for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Jun 2023 04:06:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q4w3G-0000AS-9A for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Jun 2023 04:06:10 +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 1q4w3F-0000AJ-RF for pgsql-hackers@lists.postgresql.org; Fri, 02 Jun 2023 04:06:09 +0000 Received: from mail-oa1-x2a.google.com ([2001:4860:4864:20::2a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q4w3C-003BiN-FH for pgsql-hackers@postgresql.org; Fri, 02 Jun 2023 04:06:08 +0000 Received: by mail-oa1-x2a.google.com with SMTP id 586e51a60fabf-1a26f26ebb8so1475914fac.2 for ; Thu, 01 Jun 2023 21:06:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neon-tech.20221208.gappssmtp.com; s=20221208; t=1685678765; x=1688270765; h=in-reply-to:references:message-id:from:to:subject:date :content-transfer-encoding:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=/2HLk4PnUMHHYJZ52FcztsGHAxIXyRAeA1AkSstZZWM=; b=ZXdM8Y1swpGIXf1n9hGnWQb9DJqUGHmFDUxKRQY4OAOHRhQ0Q36nsQatofwmZ2y2E2 i281w7TiL7Q7hweoFlKRyCYKgaDkUagDsmKqB2+hjg2qe0hoNbbpOVGKheSnlmzx3Whl buoTbZ+w7nA+6xi5LWANcorifGHjT7/BbSqR3FhFZ0eZ4SwEsdMH4hTcxH9dDY7jX1sd SBWOXdn0DVNHcj17EkgidMmCJCMLKPwniw8nfNyPoY4B3o5WT7GYkJqDXQMzP9eOvwKG /kBtwCkxnii7VH6kBAu3KvuUuNS7YEerOZ4KEvHoTie2LD4K1Ggyo8DbX7hvCFlfTad6 MPmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685678765; x=1688270765; h=in-reply-to:references:message-id:from:to:subject:date :content-transfer-encoding:mime-version:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=/2HLk4PnUMHHYJZ52FcztsGHAxIXyRAeA1AkSstZZWM=; b=DP1y/LWnbkkB+p/pPE9OHCSBECyMppXDHIY32SCcrg9JvxzS1J0O6Mi+ozZZn/93aQ Vf7LA/aWNuS80B69n3iEO8NR84C5auXlneIir114EkB39S7OFGYmLLc0VVhDh+G+TxX0 +KbC5JApOmd5X+nj4RU5chxu1G0X3IUeLNDhavk+96ryXlQfaGvML2isiO/wyKCXTaFU dKJBlPBF2dRYb1k6uBB9+ox0ZB67HHL5T9o674PAyVHz3HIv+7VxQKBZmR+2zekdRNAF E7p2Sb9l7f6tUV4MLSy+diT9dn9y9lwNh766/IQ4u294xqgWWBH7mEGmhzCahM4t06b0 0GFQ== X-Gm-Message-State: AC+VfDwQJZNXL0a+BIdKHf4FhGbDwGhQLQ9lQ7fJCCHBdYwKdJZvB2eY xyPXxjQSaKfQXmkBaeLdmzLEzdZmvmIR9Tmc+xY= X-Google-Smtp-Source: ACHHUZ6AiZZYl+G/GrebWORT7IvoS4ExkXsP6a8WnDw+YQY5at7YN/m875J7Cly8/87IgRtOF+Uhgg== X-Received: by 2002:a05:6870:b245:b0:19f:880f:9bb with SMTP id b5-20020a056870b24500b0019f880f09bbmr1013653oam.42.1685678765607; Thu, 01 Jun 2023 21:06:05 -0700 (PDT) Received: from localhost ([2607:fb90:e696:c1dc:3996:e070:71ee:42fb]) by smtp.gmail.com with ESMTPSA id d8-20020a4aa588000000b005552e4d405bsm131248oom.20.2023.06.01.21.06.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 01 Jun 2023 21:06:05 -0700 (PDT) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 01 Jun 2023 23:06:04 -0500 Subject: Re: [PATCH] Missing dep on Catalog.pm in meson rules To: =?utf-8?q?Dagfinn_Ilmari_Manns=C3=A5ker?= , "PostgreSQL Hackers" From: "Tristan Partin" Message-Id: X-Mailer: aerc 0.15.2-33-gedd4752268b2 References: <87v8g7s6bf.fsf@wibble.ilmari.org> <329a690c-1f4e-4759-8018-8ee562c159f0@app.fastmail.com> In-Reply-To: <329a690c-1f4e-4759-8018-8ee562c159f0@app.fastmail.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu Jun 1, 2023 at 4:22 PM CDT, Dagfinn Ilmari Manns=C3=A5ker wrote: > On Thu, 1 Jun 2023, at 22:16, Tristan Partin wrote: > > Could you create a variable for the file instead of calling files() 3 > > times? > > > >> catalog_pm =3D files('path/to/Catalog.pm') > > Sure, but which meson.build file should it go in? I know nothing about me= son variable scoping. Not a problem. In Meson, variables are globally-scoped. You can use unset_variable() however to unset it. In our case, we should add the ^line to src/backend/catalog/meson.build. I would say just throw the line after the copyright comment. Hopefully there isn't a problem with the ordering of the Meson file tree traversal (ie the targets you are changing are configured after we get through src/backend/catalog/meson.build). --=20 Tristan Partin Neon (https://neon.tech)