From: Patrick Steinhardt <ps@pks.im>
Date: Mon, 05 Oct 2026 10:25:04 GMT
Subject: Re: [PATCH 6/7] meson: update wrappers
Message-ID: <asN7AJdVmPCzov7l@pks.im>
In-Reply-To: <3de4ba2b-9b0c-499b-98bb-7077e0d7613b@gmail.com>

On Mon, Oct 05, 2026 at 03:12:34PM +0530, Kaartic Sivaraam wrote:
> On 9/24/26 19:39, Patrick Steinhardt wrote:
> > diff --git a/subprojects/openssl.wrap b/subprojects/openssl.wrap> index
> 873d55106e..e775bb104f 100644
> > --- a/subprojects/openssl.wrap
> > +++ b/subprojects/openssl.wrap
> > @@ -1,15 +1,14 @@
> >   [wrap-file]
> > [ snip ]> -wrapdb_version = 3.0.8-3
> > [ snip ]> +wrapdb_version = 3.0.10-1
> > 
> 
> We are using the latest versions from the wrap DB for the above but the
> versions available via wrap DB itself appears quite old. For instance,
> 
> - curl 8.12.1 was released on Feb/2025. The latest available
>   is 8.22.0 (released Sep/2026)
> 
> - OpenSSL 3.0.10 was released on Aug/2023. The latest available are
>   3.0.22 (released Aug/2026) and 4.0.1 (released Jun/2026).
> 
> Is this version gap something we need to document / think about?

Maybe, but I think the proper way to fix this would be to update the
wrap DB if we really care about this. For now we only use this so that
we can have a mostly dependencyless Windows build with GitLab CI. I
don't think anybody uses this for a production-facing build.

So I'd leave this as-is for now, but agree that we should maybe iterate
a bit on this going forward and collaborate with upstream.

Thanks!

Patrick