Noah Misch <n...@leadboat.com> writes:
> On Sun, Feb 16, 2025 at 08:42:50PM -0500, Andres Freund wrote:
>> On macos we can't currently use images, so we just cache all the installed 
>> macports packages. The cache is keyed by OS version and list of packages to 
>> be installed, with no other forced invalidation right now. So it's hard to 
>> predict when a new version of a package will be picked up and it will differ 
>> between git repositories.  I've been wondering whether the cached macports 
>> install should just be regularly generated instead, along the other ci 
>> images.

> The change is not in a release yet.  We could have macos install IPC::Run from
> github, or I could get a release cut so it can make its way to macports.
> https://ports.macports.org/port/p5.34-ipc-run/builds/ suggests it ingested the
> last release within a couple days of release, so macports itself may add
> negligible latency.

Yeah, my experience is that macports is pretty quick about picking up
new releases.  If you can persuade upstream to make a release happen,
that'd be great.

                        regards, tom lane


Reply via email to