Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sMFFG-001JR7-He for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Jun 2024 23:06:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sMFFE-000ptg-UZ for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Jun 2024 23:06:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sMFFE-000ptY-Co for pgsql-hackers@lists.postgresql.org; Tue, 25 Jun 2024 23:06:36 +0000 Received: from mail-pg1-x52f.google.com ([2607:f8b0:4864:20::52f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sMFFB-003YT4-Lw for pgsql-hackers@postgresql.org; Tue, 25 Jun 2024 23:06:36 +0000 Received: by mail-pg1-x52f.google.com with SMTP id 41be03b00d2f7-7226821ad86so790932a12.2 for ; Tue, 25 Jun 2024 16:06:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1719356791; x=1719961591; darn=postgresql.org; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=uYAslxVLHopD9VKXKyr7OXcAH/jiX9PmVk11qYQKKQ0=; b=TlPPpqS8ZQG/NqsPo/jG2DSGYv714l//m1Rs5iKFJvoIwY2d1aE6m0IvasDHHQILln q4jnVCeWsPhXkxYVFR7Re3TpLQ3Q90TVNctvXivaZnUuPaIq+kp4AMf3loLAYX6vC/RU PZ4vn9ugFhysqHKooiObCkH6gdctN1S/cXKj0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719356791; x=1719961591; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=uYAslxVLHopD9VKXKyr7OXcAH/jiX9PmVk11qYQKKQ0=; b=GI9bJb8m6qTUHgFLZXDOg3YQE4gPjVc0RSkCVnhLX7yVqw+VOx3H52YKkwI1ZceLDM 9YppIoyOpgEyeUfbE5L3jdf1y9o1hBX/AHRlTVKuFRmZZfR8lOUb8PKu+mKe8hWPwwfv JQloMN1i3fxLUjVT2YkupC9xQKM4IX+BHiIzIkdvcZioNSXLAmHJ1o3YYwddx5xard+b caL2P59Zdpp30IFkUIAyKopA/q2/ymN49DNlkL0dhqzjYvqvOG8MyWIaXDnxehDKnmTz hK6wzgUTc5sZtMiufB1F9dY8JK1/ASrO3wDML74qveUqimaGRPQGosFSnJk1uX84JoMq PtZQ== X-Gm-Message-State: AOJu0YyIzMFhFRL20J3VL2w+HctbIeM63ieI+a5mDFueLGTKQvARqsBr 9+FUY0Fi5IK8+Z1Fyu2UYU7cPB4ZPOMbvs/uBSNFHlmFUtLt7+VGm5lnuKM5ewBxlxwY/0lAs9E = X-Google-Smtp-Source: AGHT+IEZGlpvFSYOtlanWU5hQ//zyw5vLoyCfyOz1CzNTbytaL4xfCYbwmvYLFTnXSH/s4WYMdNCUQ== X-Received: by 2002:a05:6a20:7a28:b0:1b6:d979:fb38 with SMTP id adf61e73a8af0-1bcf7eece4cmr7062895637.31.1719356790643; Tue, 25 Jun 2024 16:06:30 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7065107ad0asm8657799b3a.36.2024.06.25.16.06.30 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Jun 2024 16:06:30 -0700 (PDT) Date: Tue, 25 Jun 2024 16:06:28 -0700 From: Noah Misch To: Robert Haas Cc: pgsql-hackers@postgresql.org Subject: Re: IPC::Run accepts bug reports Message-ID: <20240625230628.8f@rfd.leadboat.com> References: <20240615234824.a9@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Jun 17, 2024 at 01:56:46PM -0400, Robert Haas wrote: > On Sat, Jun 15, 2024 at 7:48 PM Noah Misch wrote: > > Separating this from the pytest thread: > > > > On Sat, Jun 15, 2024 at 01:26:57PM -0400, Robert Haas wrote: > > > The one > > > thing I know about that *I* think is a pretty big problem about Perl > > > is that IPC::Run is not really maintained. > > > > I don't see in https://github.com/cpan-authors/IPC-Run/issues anything > > affecting PostgreSQL. If you know of IPC::Run defects, please report them. > > If I knew of an IPC::Run defect affecting PostgreSQL, I likely would work on > > it before absurdity like https://github.com/cpan-authors/IPC-Run/issues/175 > > NetBSD-10-specific behavior coping. > > I'm not concerned about any specific open issue; my concern is about > the health of that project. https://metacpan.org/pod/IPC::Run says > that this module is seeking new maintainers, and it looks like the > people listed as current maintainers are mostly inactive. Instead, > you're fixing stuff. That's great, but we ideally want PostgreSQL's > dependencies to be things that are used widely enough that we don't > end up maintaining them ourselves. That's reasonable to want. > I apologize if my comment came across as disparaging your efforts; > that was not my intent. It did not come across as disparaging.