On Fri, Jul 08, 2022 at 09:36:11AM +0100, Stuart Henderson wrote: > On 2022/07/08 08:28, Klemens Nanni wrote: > > On Fri, Jul 08, 2022 at 12:33:18AM +0200, Theo Buehler wrote: > > > You need libcrypto.so.49.1 for this to build since I added the missing > > > X509_VERIFY_PARAM_get_time() in today's bump. There's a bit of patching, > > > but I think it's not too bad. If this works for your purposes, I guess > > > that'd be preferable over linking against eopenssl11. > > > > Would it make sense to import with `crypto>=49.1' in WANTLIB? > > Will be always true pretty soon but doesn't hurt and sort of documents > > tb's efforts. > > No big objection to that, but personally I'd only do this if either > 1. the port will actually build with the older version but produce > broken results, or 2. there's a messy situation such that two > different versions of the same named library exist and you need > to distinguish between them (as with databases/db). > > Otherwise it's just extra cognitive load when updating or syncing > wantlib, and it's easy for a future update to a port to need something > added in a newer library version (typically nobody updates them later > when this happens so the version check becomes meaningless).
That makes sense, then I won't add any version spec, thanks.
