Re: Updating IPC::Run in CI? - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Updating IPC::Run in CI?
Date
Msg-id CAOYmi+=roEb2txm4Zj383awyJh_-XY8S1Oyb06t7EZr99QQxOQ@mail.gmail.com
Whole thread Raw
In response to Re: Updating IPC::Run in CI?  (Noah Misch <noah@leadboat.com>)
Responses Re: Updating IPC::Run in CI?
List pgsql-hackers
On Mon, Nov 17, 2025 at 12:22 PM Noah Misch <noah@leadboat.com> wrote:
> It's a CPAN-managed key.  See if the key here gives what you need:
> http://pgpkeys.eu/pks/lookup?search=071B468507812067912B951258FDA3CBB759E5C4&fingerprint=on&op=index

It does, thanks, though I was surprised to see that I had to override
Module::Signature's defaults to get it to be used. gpg.conf was
ignored. So shouldn't Module::Signature default to a keyserver that
CPAN actually uses...?

> If it helps, you don't actually need to run an installation process on
> IPC::Run.  You can just unpack the tarball and add $PWD/IPC-Run/lib to the
> PERL5LIB envar.

I can't quite decide whether that would make things easier or harder.
The CPAN approach has been a lot of yak shaving, but once it works, it
should hopefully work the same across all the platforms...

Thanks,
--Jacob



pgsql-hackers by date:

Previous
From: ocean_li_996
Date:
Subject: Re: minor improvement in snapbuild: use existing interface and removefake code
Next
From: Nathan Bossart
Date:
Subject: Re: postgresql.conf.sample tab width