Re: Updating IPC::Run in CI?
| От | Noah Misch |
|---|---|
| Тема | Re: Updating IPC::Run in CI? |
| Дата | |
| Msg-id | 20251118171438.c9.nmisch@google.com обсуждение исходный текст |
| Ответ на | Re: Updating IPC::Run in CI? (Jacob Champion <jacob.champion@enterprisedb.com>) |
| Список | pgsql-hackers |
On Tue, Nov 18, 2025 at 08:29:14AM -0800, Jacob Champion wrote: > 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...? Yes, Module::Signature should do that, or the key should be on more keyservers, or both. More keyservers would always be a good thing anyway for such a prominent key. > > 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... Yep. Whichever works better for you.
В списке pgsql-hackers по дате отправления: